After cluster cloning management network ranges are different
Bug #1495987 reported by
Egor Kotko
This bug report is a duplicate of:
Bug #1483773: [nailgun]Clone environment doesn't clone environment 'ip_ranges' settings properly.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Confirmed
|
High
|
Ilya Kharin | ||
| 7.0.x |
Won't Fix
|
High
|
Fuel Python (Deprecated) | ||
Bug Description
Scenario:
1. Revert snapshot "upgrade_
2. Clone cluster
3. Check status code
4. Check that clusters are equal
After cluster cloning management network rages are different (see the screenshot):
The UIs contain only 10.109.2.0/24 ranges both clusters, but if download network .yamls
fuel --user=admin --password=newpass network --download --env 1
fuel --user=admin --password=newpass network --download --env 2
the ranges are different: 10.109.
Revision history for this message
| Egor Kotko (ykotko) wrote | #1 |
Revision history for this message
| Egor Kotko (ykotko) wrote | #2 |
| Changed in fuel: | |
| assignee: | Fuel Library Team (fuel-library) → Fuel Python Team (fuel-python) |
| Changed in fuel: | |
| status: | New → Confirmed |
| Changed in fuel: | |
| milestone: | 7.0 → 8.0 |
Revision history for this message
| Andrey Maximov (maximov) wrote | #3 |
| Changed in fuel: | |
| assignee: | Fuel Python Team (fuel-python) → Ilya Kharin (akscram) |
| summary: |
- After cluster cloning management network rages are different + After cluster cloning management network ranges are different |
To post a comment you must log in.
moving to 8.0, because we cannot fix High bugs after HCF.