Created attachment 1034781 [details] sosreport Description of problem: hosts running affected code with DHCP configured interfaces, upon supervdsmd death will not renew the lease after its expiry i.e. disconnect from the management network Version-Release number of selected component (if applicable): discovered on vdsm-4.17.0.4-1.el7ev.noarch and 4.16.x vdsm hosts, master is affected too. How reproducible: It was discovered upon host reinstallation in d/s jenkins jobs that did yum remove vdsm*, and then install the Steps to Reproduce: 1.setup host with rhevm configured via dhcp [default config] 2.login into host and run: systemctl stop supervdsm 3.wait for lease to expire Actual results: Upon supervdsm service stopped (or killed) dhclient is dead [killed on duty by systemd] host disconnects after the lease expires. Expected results: network connectivity unaffected Additional info:
Reproduction: 1. Use setupNetworks to define a network with dhcp. This creates a dhclient process that extends the lease when needed. 2. if supervdsmd is stopped (due to a bug or an upgrade or an admin decision) dhclient is killed (and the lease would not be extended). 3. even if vdsm is restarted, it does not re-create the dhclient process
This is awfully similar to bug 1201355, and a similart hack - of running ifup in a separate cgroup - may fix it.
Tested and Verified with - vdsm-4.17.7-1.el7ev.noarch vdsm-4.16.27-1.el7ev.x86_64