Bug 1206536

Summary:	vdsm-3.5 network conf upgrade fails, due to `service network restart` by node
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	rhev-integ
Component:	rhev-hypervisor	Assignee:	Fabian Deutsch <fdeutsch>
Status:	CLOSED ERRATA	QA Contact:	Meni Yakove <myakove>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	3.5.0	CC:	adevolder, anande, bazulay, cshao, danken, ecohen, fdeutsch, gchakkar, hadong, huiwa, iheim, jason.bramwell, leiwang, lmiccini, lpeer, lsurette, mburman, meverett, mfagan, mkalinin, myakove, nashok, pablo.iranzo, pdwyer, pstehlik, rbarry, rhodain, rmcswain, s.kieske, syangsao, troels, yaniwang, ycui, yeylon, ylavi
Target Milestone:	---	Keywords:	ZStream
Target Release:	3.5.1	Flags:	ylavi: Triaged+
Hardware:	x86_64
OS:	Linux
Whiteboard:	node
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Previously, a race between services during boot prevented network configuration from upgrading correctly. The risk for the race has now been reduced significantly to allow the upgrade of the network configuration to complete correctly.	Story Points:	---
Clone Of:	1194068	Environment:
Last Closed:	2015-04-28 18:53:51 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Node	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1194068
Bug Blocks:

Comment 2 cshao 2015-03-30 05:33:32 UTC

RHEV-H 6.6 host can UP after upgrade from rhevh 6.5, and all "ONBOOT" parameters  show as "yes".

Test version:
RHEVH 6.5 20150115
rhev-hypervisor6-6.6-20150327.0
ovirt-node-3.2.2-1.el6.noarch
RHEV-M VT14.1 (3.5.1-0.2.el6ev)

Test steps:
1. Installed RHEVH 6.5 20150115 with [bond+ vlan] network, add rhevh via rhevm portal into 3.4 compatibility version in rhevm 3.5.1-0.2.el6ev
2. Created 1 VM running on it successful.
3. Shutdown the 1 VM, then maintenance the rhevh 6.5 host.
4. Upgrade rhevh 6.5 via rhevm portal to rhev-hypervisor6-6.6-20150327.0

Test result:
1. RHEV-H 6.6 host can UP after RHEV-H 6.5 upgrade to RHEV-H 6.6.
2. ONBOOT stays as the previously set value of yes.

So the bug is fixed, change bug status to VERIFIED.

Comment 3 cshao 2015-04-03 04:35:43 UTC

Double check with latest build rhev-hypervisor6-6.6-20150402.0.el6ev.

Test version:
RHEVH 6.5 20150115
rhev-hypervisor6-6.6-20150402.0
ovirt-node-3.2.2-3.el6.noarch
RHEV-M VT14.2 (3.5.1-0.3.el6ev)

Test steps:
1. Installed RHEVH 6.5 20150115 with [bond+ vlan] network, add rhevh via rhevm portal into 3.4 compatibility version.
2. Created 1 VM running on it successful.
3. Shutdown the 1 VM, then maintenance the rhevh 6.5 host.
4. Upgrade rhevh 6.5 via rhevm portal to rhev-hypervisor6-6.6-20150402.0

Test result:
1. RHEV-H 6.6 host can UP after RHEV-H 6.5 upgrade to RHEV-H 6.6.
2. ONBOOT stays as the previously set value of yes.

So the bug is fixed with above build.

Comment 12 errata-xmlrpc 2015-04-28 18:53:51 UTC

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.

https://rhn.redhat.com/errata/RHBA-2015-0903.html