[upgrades] UpgradeHelper methods do not work with network template

Bug #1568782 reported by Aleksey Kasatkin
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Won't Fix
High
Ilya Kharin
Mitaka
Won't Fix
High
Ilya Kharin
Newton
Won't Fix
High
Ilya Kharin

Bug Description

Versions: Fuel 7.0 and later.

UpgradeHelper methods "copy_network_config" and "copy_vips" do not work properly in case of using network template.

Network roles to networks mapping and custom names of networks (that can be changed when using network template) are not considered in "copy_vips" method.
Network template is not copied and custom networks and not copied in "copy_network_config" method.

So, environments that were deployed using network templates cannot be upgraded.

Changed in fuel:
assignee: nobody → Fuel Python Team (fuel-python)
assignee: Fuel Python Team (fuel-python) → Ilya Kharin (akscram)
Changed in fuel:
importance: Undecided → High
Changed in fuel:
status: New → Confirmed
Revision history for this message
Oleg S. Gelbukh (gelbuhos) wrote :

Here we need to implement a handle in API extension to explicitly specify the list of VIPs that has to be preserved in the upgraded environment.

Revision history for this message
Anton Matveev (amatveev) wrote :

current issue does not affect existing tests and relates to limited group of deployments (with networking templates), can be safely moved to maintenance release and delivered with MU1

tags: added: move-to-mu
Revision history for this message
Ilya Kharin (akscram) wrote :

This bug is partially fixed by the next bug reports:
    https://bugs.launchpad.net/fuel/+bug/1612297
    https://bugs.launchpad.net/fuel/+bug/1616817
    https://bugs.launchpad.net/fuel/+bug/1584044
    https://bugs.launchpad.net/fuel/+bug/1612297
This bug can be moved to 9.2 without affecting the current functionlity.

Revision history for this message
Anton Matveev (amatveev) wrote :

octane specific, moving to won't fix due to shifted priorities

Changed in fuel:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.