Created attachment 1096671 [details] engine, vdsm and supervdsm logs Description of problem: When calling setupNetwork the operation sometimes fails with error: MainProcess|Thread-22381::ERROR::2015-11-18 14:44:30,017::utils::148::root::(rmFile) Removing file: /etc/sysconfig/network-scripts/ifcfg-case4_net1 failed Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 142, in rmFile os.unlink(fileToRemove) OSError: [Errno 16] Device or resource busy: '/etc/sysconfig/network-scripts/ifcfg-case4_net1' MainProcess|Thread-22381::ERROR::2015-11-18 14:44:30,018::supervdsmServer::118::SuperVdsm.ServerCallback::(wrapper) Error in setupNetworks Traceback (most recent call last): File "/usr/share/vdsm/supervdsmServer", line 116, in wrapper res = func(*args, **kwargs) File "/usr/share/vdsm/supervdsmServer", line 241, in setupNetworks return setupNetworks(networks, bondings, **options) File "/usr/share/vdsm/network/api.py", line 942, in setupNetworks options, logger) File "/usr/share/vdsm/network/configurators/__init__.py", line 60, in __exit__ leftover = self.rollback() File "/usr/share/vdsm/network/configurators/ifcfg.py", line 83, in rollback self.configApplier.restoreBackups() File "/usr/share/vdsm/network/configurators/ifcfg.py", line 466, in restoreBackups self.restoreAtomicBackup() File "/usr/share/vdsm/network/configurators/ifcfg.py", line 389, in restoreAtomicBackup utils.rmFile(confFilePath) File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 142, in rmFile os.unlink(fileToRemove) OSError: [Errno 16] Device or resource busy: '/etc/sysconfig/network-scripts/ifcfg-case4_net1' Version-Release number of selected component (if applicable): Red Hat Enterprise Virtualization Hypervisor (Beta) release 7.2 (20151112.1.el7ev) Steps to Reproduce: 1. Run TestSanityCase13 from network sanity automation
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Steps to Reproduce: 1. Create VM network and attach it to host NIC 2. Change the network to be non-VM 3. Change the network to be VM network
reproduction steps: 1. Install ovirt-node/RHEVH and connect to engine. 2. Change in the management network IP of the node to something different. The node starts rolling back and fails because of error above.
should this be POST?
yes https://gerrit.ovirt.org/#/c/48841/1
This bug is referenced in 4.17.12 git log and has target release unset. Please check
Verified on - 3.6.1.1-0.1.el6 with: vdsm-4.17.12-0.el7ev.noarch Red Hat Enterprise Virtualization Hypervisor (Beta) release 7.2 (20151201.2.el7ev) ovirt-node-3.6.0-0.23.20151201git5eed7af.el7ev.noarch
According to verification status and target milestone this issue should be fixed in oVirt 3.6.1. Closing current release.