29efa4a3e7
If we change configuration files right after installing service
packages, automatically started services may pick up changed
configuration files rather than the default files they were packaged
with.
If the neutron-l3-agent starts with our custom configuration file which
refers to the external bridge br-ex while that bridge is not there
(yet), the port is permanently marked as unavailable (vlan tag=4095).
In such a case, a line like this can be found in /etc/openvswitch/conf.db:
{"_date":1435514607570,
"Port":{"20b0e96c-6103-46e6-a234-a4d5439eece7":{"tag":4095}}, "_comment":"
ovs-vsctl: /usr/bin/ovs-vsctl --timeout=10 set Port qr-4be1ab91-60 tag=4095"
,"Open_vSwitch":{"e00f3d6f-e55a-419a-a605-141021026dee":{"next_cfg":15}}}
For additional information, check this neutron bug:
Neutron openvswitch-agent doesn't recover ports from binding_failed status
https://bugs.launchpad.net/neutron/+bug/1399249
This is another race -- waiting for a few seconds before changing the
configuration files fixes the problem. The alternative used in this
patch is to stop the neutron-l3-agent before editing the configuration
files and to start it only once the bridge is ready.
Change-Id: I55762d17817e5e1cdb4c0420374c9fbc314bdff1
Co-Authored-By: Vigneshvar.A.S <vigneshvar.a.s@gmail.com>
Co-Authored-By: sayalilunkad <sayali.92720@gmail.com>
All scripts in this directory run within the VMs.
They install and configure OpenStack components and any other required software (such as databases).
Before these generic scripts run, scripts from the osbash subdirectory set up the VM and configure basic networking.