Change to linuxbridge agent defaults affects upgrades
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Invalid
|
Undecided
|
Unassigned | ||
Liberty |
Triaged
|
Medium
|
Unassigned |
Bug Description
Upgrading from r11.1.3 to 12.0.8 using the documentation found at:
http://
Changes to the LinuxBridge agent defaults negatively impacts upgrades if the config options are not called out in the user_variables file.
In this case, the following was in place prior to the upgrade:
[vxlan]
l2_population = True
After the upgrade, the following was in place:
[vxlan]
l2_population = False
This caused any new virtual machine on a vxlan network to not be accessible after the upgrade. The jinja template appears to make that setting configurable (Yay!) but the default is set to False here without regards to the original setting (boo!):
Updating /etc/openstack_
Changed in openstack-ansible: | |
status: | New → Triaged |
importance: | Undecided → Medium |
assignee: | nobody → admin0 (shashi-eu) |
milestone: | none → 13.0.1 |
milestone: | 13.0.1 → 12.0.10 |
Changed in openstack-ansible: | |
milestone: | 12.0.10 → 12.1.0 |
status: | Triaged → Invalid |
milestone: | 12.1.0 → none |
importance: | Medium → Undecided |
assignee: | admin0 (shashi-eu) → nobody |
Review: https:/ /review. openstack. org/301759