auto allocate external network callback changes is_default
Bug #1670524 reported by
Kevin Benton
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
Fix Released
|
High
|
Armando Migliaccio | ||
Bug Description
The code at [1] always gets executed on a network update so if you perform a network update to update something unrelated to the 'is_default' column, 'is_default' will be changed to False. So completely unrelated network updates end up clearing the is_default value.
| Changed in neutron: | |
| assignee: | nobody → Armando Migliaccio (armando-migliaccio) |
| importance: | Undecided → High |
| Changed in neutron: | |
| status: | New → Confirmed |
| tags: | added: auto-allocated-topology |
Revision history for this message
| Armando Migliaccio (armando-migliaccio) wrote | #1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to neutron (master) | #2 |
| Changed in neutron: | |
| status: | Confirmed → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to neutron (master) | #3 |
| Changed in neutron: | |
| status: | In Progress → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/neutron 11.0.0.0b1 | #4 |
To post a comment you must log in.
https:/