Remove ml2_conf.ini from ML2 agent init scripts
Bug #1512531 reported by
Matt Kassawara
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Won't Fix
|
Low
|
Travis Truman |
Bug Description
In Liberty onwards, remove ml2_conf.ini from Linux bridge agent init script because configuration resides completely in linuxbridge_
Likewise, in Newton onwards, remove ml2_conf.ini from the Open vSwitch agent init script because configuration should reside completely within openvswitch_
Changed in openstack-ansible: | |
assignee: | nobody → Matt Kassawara (ionosphere80) |
milestone: | none → mitaka-1 |
importance: | Undecided → Low |
Changed in openstack-ansible: | |
milestone: | mitaka-1 → none |
Changed in openstack-ansible: | |
status: | Incomplete → Won't Fix |
To post a comment you must log in.
In testing right before the kilo release doing this lead to issues with metadata and agent stability causing us to disable apr spoofing protection in order to pass the gate. I think that the intentions are good in simplifying configs I think there are some issues with it still and sourcing both files simply ensures that all of the appropriate configs are loaded as expected. If there's something that we can do in the various configuration files to make this more feasible than I'm certainly game to make the update however I'd rather error on the side of caution in most cases.