Floating range change fails during redeployment
Bug #1569286 reported by
Alexey Shtokolov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Invalid
|
High
|
Fuel Library (Deprecated) | ||
| Mitaka |
Invalid
|
High
|
Fuel Library (Deprecated) | ||
Bug Description
Fuel versions: Mitaka, Newton
Steps to reproduce:
1. Deploy the cluster
2. Change CIDR for public network (it leads to the same change for floating network)
3. Press Deploy Changes
Expected results:
Redeployment changes CIDR for public/floating network
Actual results:
openstack_
Property cidr does not support being updated
(/Stage[
| tags: |
added: area-library removed: area-llibrary |
| Changed in fuel: | |
| status: | New → Confirmed |
| tags: |
added: feature-granular-task-lcm-readiness removed: feature-idempotnecy |
Revision history for this message
| Michael Polenchuk (mpolenchuk) wrote | #1 |
Revision history for this message
| Ivan Ponomarev (ivanzipfer) wrote | #3 |
| Changed in fuel: | |
| status: | Confirmed → Incomplete |
| status: | Incomplete → Invalid |
To post a comment you must log in.
Actually neutron subnet-update doesn't support the change of cidr.
The only way to do this is "remove subnet" then add it with new cidr.