Bug 1267500

Summary: vdsm fails to start if dhclient is running
Product: Red Hat Enterprise Virtualization Manager Reporter: rhev-integ
Component: vdsmAssignee: Petr Horáček <phoracek>
Status: CLOSED ERRATA QA Contact: Meni Yakove <myakove>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 3.5.4CC: adahms, bazulay, cshao, cwu, danken, ecohen, fdeutsch, gklein, huiwa, juwu, leiwang, lsurette, mburman, myakove, pdwyer, phoracek, ycui, yeylon, ylavi
Target Milestone: ovirt-3.5.6Keywords: ZStream
Target Release: 3.5.6   
Hardware: x86_64   
OS: Linux   
Whiteboard: network
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previously, when starting a configured but non-active VDSM device, for example if a device was manually set to down, the VDSM service executed the 'service network start' command instead of the 'service network restart' command. If the device was also running DHCP, the dhclient was started twice and led to VDSM service start failure. With this update, 'service network restart' is actually run so if DHCP was running on the device, the dhclient it not started a second time, and the VDSM service starts as normal.
Story Points: ---
Clone Of: 1258551 Environment:
Last Closed: 2015-12-01 20:40:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1258551    
Bug Blocks:    

Comment 2 Michael Burman 2015-11-01 13:18:11 UTC
Verified on - 3.5.6.1-0.1.el6ev
with:
vdsm-4.16.28-1.el6ev.x86_64
vdsm-4.16.28-1.el7ev.x86_64

Comment 3 Julie 2015-11-11 00:42:05 UTC
If this bug requires doc text for errata release, please provide draft text in the doc text field in the following format:

Cause:
Consequence:
Fix:
Result:

The documentation team will review, edit, and approve the text.

If this bug does not require doc text, please set the 'requires_doc_text' flag to -.

Comment 4 Julie 2015-11-12 00:01:00 UTC
Hi Petr,
     Thanks for providing the draft doc text. Could you explain a bit more the following text: 'it finds difference between `service network status` Active and Configured devices..'
so I guess I still don't understand why service network start is run instead in the background.

Kind regards,
Julie

Comment 5 Julie 2015-11-15 23:09:44 UTC
Haven't heard back from the need_info request. Therefore updating the doc text to my understanding.

Cheers,
Julie

Comment 6 Petr Horáček 2015-11-20 11:19:08 UTC
Sorry it took me so long. I changed it

Comment 7 Petr Horáček 2015-11-20 11:20:30 UTC
(continuing with comment sent by mistake)...

now it should describe the problem a bit better.

Comment 9 errata-xmlrpc 2015-12-01 20:40:41 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-2530.html