[GENIUS-213] vxlan tep tunnels are not being created Created: 16/Oct/18 Updated: 23/Oct/18 Resolved: 23/Oct/18 |
|
| Status: | Resolved |
| Project: | genius |
| Component/s: | ITM |
| Affects Version/s: | None |
| Fix Version/s: | Fluorine-SR1 |
| Type: | Bug | Priority: | Highest |
| Reporter: | Sam Hague | Assignee: | Faseela K |
| Resolution: | Done | Votes: | 0 |
| Labels: | csit:failures | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
The majority of the test suites fail in suite setup because the vm instances cannot get an ip address on the vxlan networks. This looks to be due to the itm tep tunnels not coming up as shown in the first url below - at this point the tunnels need to be created but they are not. So any networks using the vxlan overlay fail for ip assignment to vms since there is no overlay. |
| Comments |
| Comment by Sam Hague [ 16/Oct/18 ] |
|
possibly the gerrit below from genius is the culprit. I tried to track down where this problem popped up and found some issues around 9/11 - which the patch below was cherry-picked to fluorine. Not sure if it really is the problem beyond the timing. |
| Comment by Sam Hague [ 23/Oct/18 ] |
|
This ended up being a deployment problem. The neon distros were being used in the fluorine jobs. Using the correct fluorine distro fixed the issue. |