Red Hat Bugzilla – Bug 1252061
rhev-h might restore its management network on every reboot
Last modified: 2016-02-10 14:16:20 EST
Description of problem:
If a rhev-h host is registered in engine via tui, a management network restoration will happen on each successive reboot although the network was not changed.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. register a node on an engine (via tui) in 3.5.3.
2. upgrade to 3.5.4
VDSM will restore the management network
no network should be restored since in 3.5.4 VDSM does not restore networks that are identical to their persisted configuration.
This is a regression in 3.5.4. until 3.5.4, the management network was the only network configured with ONBOOT=yes. Now, although all the networks are configured that way, VDSM will insist on reconfiguring it on every boot. If, in addition, this network shares a nic with another network (may it be used for storage, migration etc.) will also be disconnected during this restoration.
Verified on - 3.5.5-0.1.el6ev with -->
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.