LBaaS: apply default provider for existing pools
Bug #1220606 reported by
Oleg Bondarev
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Expired
|
Medium
|
Unassigned |
Bug Description
For pools that were created before service providers support 'provider' field is empty. This causes neutron start failure with the following error:
Delete associated loadbalancer pools before removing providers ['']
I think that for such pools we can safely apply the default provider (haproxy) on start as it is the only provider supported at the moment.
Changed in neutron: | |
milestone: | none → havana-3 |
Changed in neutron: | |
milestone: | havana-3 → havana-rc1 |
tags: | added: havana-rc-potential |
Changed in neutron: | |
milestone: | havana-rc1 → none |
tags: |
added: havana-backport-potential removed: havana-rc-potential |
tags: | removed: havana-backport-potential |
Changed in neutron: | |
assignee: | Oleg Bondarev (obondarev) → nobody |
status: | In Progress → Incomplete |
To post a comment you must log in.
That should have been addressed by the ability of having unassociated pools plus the ability to associate provider.
Need to revisit the logic in Icehouse and make it more flexible.