Wrong network configuration on controllers after install MU

Bug #1549692 reported by Vadim Rovachev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
Critical
Vadim Rovachev

Bug Description

After install cluster with updated fuel master node and enabled proposed, updates and security mirrors we have broken networks:
https://paste.mirantis.net/show/1908/
But on updated cluster using enabled proposed, updates and security mirrors but without updated master nodes we have cluster with worked networks:
https://paste.mirantis.net/show/1909/

It seems that this is due to a bug:
https://bugs.launchpad.net/fuel/+bug/1510072
but nodes not rebooted

Tags: need-info
Changed in fuel:
importance: Undecided → Critical
assignee: nobody → MOS Maintenance (mos-maintenance)
milestone: none → 7.0-updates
Changed in fuel:
status: New → Confirmed
milestone: 7.0-updates → 7.0-mu-3
Revision history for this message
Vitaly Sedelnik (vsedelnik) wrote :

Looks to be a duplicate of https://bugs.launchpad.net/fuel/+bug/1548248 - Vadim, please take a look

Changed in fuel:
assignee: MOS Maintenance (mos-maintenance) → Vadim Rovachev (vrovachev)
Changed in fuel:
milestone: 7.0-mu-3 → 9.0
Revision history for this message
Bug Checker Bot (esikachev-l) wrote : Autochecker

(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:

actual result

version

expected result

steps to reproduce

For more detailed information on the contents of each of the listed sections see https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Here_is_how_you_file_a_bug

tags: added: need-info
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.