Bug 1196220

Summary: Track dhcp RHEV-H 7.0 bug
Product: Red Hat Enterprise Virtualization Manager Reporter: Fabian Deutsch <fdeutsch>
Component: ovirt-nodeAssignee: Fabian Deutsch <fdeutsch>
Status: CLOSED NEXTRELEASE QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 3.5.0CC: cshao, ecohen, fdeutsch, gklein, hadong, huiwa, leiwang, lsurette, yaniwang, ycui
Target Milestone: ---Keywords: TestOnly
Target Release: 3.5.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: node
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-04-24 04:55:08 UTC Type: Bug
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: 1187244    
Bug Blocks:    

Description Fabian Deutsch 2015-02-25 14:11:03 UTC
A tracker to track that the dhcp bug we are seeing in RHEV-H 7.0 (see dependency bug) is also getting fixed in RHEV-H.

Comment 1 Ying Cui 2015-03-19 23:52:36 UTC
checked Bug 1187244 - [RHEL 7.0 + 7.1] Host configure with DHCP is losing connectivity after some time - dhclient is not running

The bug 1187244 is targeted to rhev 3.5.1, so this rhevh testonly bug also need to target to rhev 3.5.1 to test it in rhevh side. Thanks.

Comment 2 Ying Cui 2015-04-24 04:08:05 UTC
Tested this bug is fixed on following version

# rpm -q ovirt-node kernel vdsm dhclient systemd
ovirt-node-3.2.2-3.el7.noarch
kernel-3.10.0-229.1.2.el7.x86_64
vdsm-4.16.13.1-1.el7ev.x86_64
dhclient-4.2.5-36.el7.x86_64
systemd-208-20.el7_1.2.x86_64

# cat /etc/rhev-hypervisor-release 
Red Hat Enterprise Virtualization Hypervisor 7.1 (20150420.0.el7ev)

Test steps:
1. Installed rhevh 7.1.
2. Setup dhcp network via rhevh tui.
3. register to rhevm 3.5.1-0.4.el6ev
4. connect nfs storage.
5. Setup VMs running on it.
6. Wait 24hrs to check the rhevh 7.1 IP and status.
7. Wait 36hrs to check the rhevh 7.1 IP and status.

Results:
After 24hrs and 36hrs, the rhevh 7.1 host did not lose ip connectivity. And rhevh 7.1 is UP in rhevm portal, VMs are running as well.

Comment 5 Fabian Deutsch 2015-04-24 04:55:08 UTC
This bug will be fixed in the next release, see also bug 1204782.