Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 432905[details]
oserror.vdsm.log
Description of problem:
the following issue happened twice so far running on particular setup (scale of 180 vsm - 3 per host), where I start to get the following messages in vdsm log:
OSError: [Errno 11] Resource temporarily unavailable
it seems like vdsm has 827 open files (using lsof) - see attachment.
when it occurs system stop to function, host goes to non-operational, and there is nothing to do (maybe kill vdsm service and try again).
Thread-6432::ERROR::2010-07-19 16:09:11,523::misc::58::irs::[Errno 11] Resource temporarily unavailable
Thread-6494::ERROR::2010-07-19 16:09:11,523::misc::59::irs::Traceback (most recent call last):
File "/usr/share/vdsm/storage/task.py", line 973, in _run
return fn(*args, **kargs)
File "/usr/share/vdsm/storage/hsm.py", line 1440, in public_getVolumeSize
apparentsize = str(volume.Volume.getVSize(sdUUID, spUUID, imgUUID, volUUID, bs=1))
File "/usr/share/vdsm/storage/volume.py", line 249, in getVSize
return mysd.getVolumeClass().getVSize(mysd, imgUUID, volUUID, bs)
File "/usr/share/vdsm/storage/blockVolume.py", line 45, in getVSize
return int(int(sdobj.vg.getLVInfo(volUUID))/bs)
File "/usr/share/vdsm/storage/vg.py", line 727, in getLVInfo
return self.lvSize(name)
File "/usr/share/vdsm/storage/vg.py", line 720, in lvSize
(rc, out, err) = self.syncExecCmd(name, cmd, exclusive=True)
File "/usr/share/vdsm/storage/vg.py", line 89, in syncExecCmd
return misc.execCmd(cmd)
File "/usr/share/vdsm/storage/misc.py", line 102, in execCmd
stdin=infile, stdout=outfile, stderr=subprocess.PIPE)
File "/usr/lib64/python2.6/subprocess.py", line 595, in __init__
if startupinfo is not None:
File "/usr/lib64/python2.6/subprocess.py", line 1009, in _execute_child
fcntl.fcntl(fd, fcntl.F_SETFD, old | cloexec_flag)
OSError: [Errno 11] Resource temporarily unavailable
we are not sure if its vdsm leak or pythons. it requires further investigation.
repro steps (might be hard to reproduce, though it happened twice, so I decided to open it).
1) make sure setup consist of a 2 hosts or more which runs 60 vms over iscsi
2) reboot libvirtd service
3) kill some of the vms with kill -9
4) start more vms
Created attachment 432905 [details] oserror.vdsm.log Description of problem: the following issue happened twice so far running on particular setup (scale of 180 vsm - 3 per host), where I start to get the following messages in vdsm log: OSError: [Errno 11] Resource temporarily unavailable it seems like vdsm has 827 open files (using lsof) - see attachment. when it occurs system stop to function, host goes to non-operational, and there is nothing to do (maybe kill vdsm service and try again). Thread-6432::ERROR::2010-07-19 16:09:11,523::misc::58::irs::[Errno 11] Resource temporarily unavailable Thread-6494::ERROR::2010-07-19 16:09:11,523::misc::59::irs::Traceback (most recent call last): File "/usr/share/vdsm/storage/task.py", line 973, in _run return fn(*args, **kargs) File "/usr/share/vdsm/storage/hsm.py", line 1440, in public_getVolumeSize apparentsize = str(volume.Volume.getVSize(sdUUID, spUUID, imgUUID, volUUID, bs=1)) File "/usr/share/vdsm/storage/volume.py", line 249, in getVSize return mysd.getVolumeClass().getVSize(mysd, imgUUID, volUUID, bs) File "/usr/share/vdsm/storage/blockVolume.py", line 45, in getVSize return int(int(sdobj.vg.getLVInfo(volUUID))/bs) File "/usr/share/vdsm/storage/vg.py", line 727, in getLVInfo return self.lvSize(name) File "/usr/share/vdsm/storage/vg.py", line 720, in lvSize (rc, out, err) = self.syncExecCmd(name, cmd, exclusive=True) File "/usr/share/vdsm/storage/vg.py", line 89, in syncExecCmd return misc.execCmd(cmd) File "/usr/share/vdsm/storage/misc.py", line 102, in execCmd stdin=infile, stdout=outfile, stderr=subprocess.PIPE) File "/usr/lib64/python2.6/subprocess.py", line 595, in __init__ if startupinfo is not None: File "/usr/lib64/python2.6/subprocess.py", line 1009, in _execute_child fcntl.fcntl(fd, fcntl.F_SETFD, old | cloexec_flag) OSError: [Errno 11] Resource temporarily unavailable we are not sure if its vdsm leak or pythons. it requires further investigation. repro steps (might be hard to reproduce, though it happened twice, so I decided to open it). 1) make sure setup consist of a 2 hosts or more which runs 60 vms over iscsi 2) reboot libvirtd service 3) kill some of the vms with kill -9 4) start more vms