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.
Description of problem:
Version-Release number of selected component (if applicable):
openlmi-providers-0.1.1-2.fc20.x86_64
How reproducible:
always
Steps to Reproduce:
1. start lmishell
2.
> c = connect("localhost", "root", "blank")
> cs = c.root.cimv2.Linux_ComputerSystem.first_instance()
> for identity in cs.associators(Role="System", ResultRole="InstalledSoftware", ResultClass="LMI_SoftwareIdentity"):
... print(identity.ElementName)
...
Now press ctrl+c:
^CTraceback (most recent call last):
File "<console>", line 1, in <module>
File "/usr/lib/python2.7/site-packages/lmi/shell/LMIDecorators.py", line 210, in wrapper
return fn(self_wr, *args, **kwargs)
File "/usr/lib/python2.7/site-packages/lmi/shell/LMIDecorators.py", line 85, in wrapper
return fn(self_wr, *args, **kwargs)
File "/usr/lib/python2.7/site-packages/lmi/shell/LMIInstance.py", line 327, in associators
associators_list = self._conn._client._get_associators(self._cim_instance, **kwargs)
File "/usr/lib/python2.7/site-packages/lmi/shell/LMIBaseClient.py", line 526, in _get_associators
return self._cliconn.Associators(instance.path, **params)
File "/usr/lib/python2.7/site-packages/pywbem/cim_operations.py", line 695, in Associators
**params)
File "/usr/lib/python2.7/site-packages/pywbem/cim_operations.py", line 167, in imethodcall
verify_callback = self.verify_callback)
File "/usr/lib/python2.7/site-packages/pywbem/cim_http.py", line 217, in wbem_request
response = h.getresponse()
File "/usr/lib64/python2.7/httplib.py", line 1045, in getresponse
response.begin()
File "/usr/lib64/python2.7/httplib.py", line 409, in begin
version, status, reason = self._read_status()
File "/usr/lib64/python2.7/httplib.py", line 365, in _read_status
line = self.fp.readline(_MAXLINE + 1)
File "/usr/lib64/python2.7/socket.py", line 476, in readline
data = self._sock.recv(self._rbufsize)
File "/usr/lib64/python2.7/ssl.py", line 241, in recv
return self.read(buflen)
File "/usr/lib64/python2.7/ssl.py", line 160, in read
return self._sslobj.read(len)
KeyboardInterrupt
> ctrl+d
3.
# yum install openlmi-software --enablerepo=rawhide
Loaded plugins: auto-update-debuginfo, langpacks, refresh-packagekit
Existing lock /var/run/yum.pid: another copy is running as pid 13721.
Another app is currently holding the yum lock; waiting for it to exit...
The other application is: cimprovagt
Memory : 274 M RSS (1.1 GB VSZ)
Started: Wed Aug 28 04:36:36 2013 - 23:12 ago
State : Running, pid: 13721
Another app is currently holding the yum lock; waiting for it to exit...
The other application is: cimprovagt
Memory : 274 M RSS (1.1 GB VSZ)
Started: Wed Aug 28 04:36:36 2013 - 23:14 ago
State : Running, pid: 13721
Actual results:
Lock is hold after lmishell ends until request is not finished in cimprovagt.
Expected results:
No locked yum? It's troubles with jobs inside software provider?
This is in fact an expected behaviour. Provider does not have any way how to find out that user doesn't want to wait for completion anymore. When operation, such as enumeration of installed packages, is started, provider has to finish it. Only then the yum lock can be released (if no other operation is running or queued).