+++ This bug was initially created as a clone of Bug #1283628 +++
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
--- Additional comment from Red Hat Bugzilla Rules Engine on 2015-11-23 11:17:02 EST ---
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.
--- Additional comment from Meni Yakove on 2015-11-24 07:01:32 EST ---
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
--- Additional comment from Sagi Shnaidman on 2015-11-29 07:38:18 EST ---
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.
--- Additional comment from Yaniv Dary on 2015-11-29 07:40:15 EST ---
should this be POST?
--- Additional comment from Sagi Shnaidman on 2015-11-29 08:16:01 EST ---
yes
https://gerrit.ovirt.org/#/c/48841/1
Comment 1Red Hat Bugzilla Rules Engine
2015-11-29 14:46:41 UTC
This bug is not marked for z-stream, yet the milestone is for a z-stream version, therefore the milestone has been reset.
Please set the correct milestone or add the z-stream flag.
Comment 2Red Hat Bugzilla Rules Engine
2015-11-29 15:00:30 UTC
This bug is not marked for z-stream, yet the milestone is for a z-stream version, therefore the milestone has been reset.
Please set the correct milestone or add the z-stream flag.
*** Bug 1286443 has been marked as a duplicate of this bug. ***
Comment 4Red Hat Bugzilla Rules Engine
2015-11-29 15:10:36 UTC
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.
Verified on - 3.5.7-0.1.el6ev
vdsm-4.16.32-1.el7ev.x86_64
ovirt-node-3.2.3-30.el7.noarch
Red Hat Enterprise Virtualization Hypervisor release 7.2 (20151229.1.el7ev)
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-2016-0034.html