VMM left in VXLAN mode despite sauto calling acc-provision to set the fabric in VLAN mode
ceridwen opened this issue · 1 comments
Earlier today I started automated tests for the VLAN and VXLAN modes. sauto failed during the reimage/OS installation step due to #17, so the test automation invoked it again to try to install in VLAN mode. This install succeeded, but the external routing tests were failing, and when I went to look at the fabric the kube VMM domain was still set in VXLAN mode, even though sauto runs acc-provision as part of the install and the acc_provision_input.yaml that sauto passed to acc-provision used VLAN mode. I tried manually reprovisioning, deleting the resources and then recreating them using the VLAN input file, but while the service tests could now reach some pods, they couldn't reach all the pods. I don't know how exactly this can happen, but we need to avoid the possibility of a fabric ending up in this broken state.
This was actually a bug in sauto.