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:
E.g.
When you use libvirt Python binding to save a domain, if the domain saving fails on send "stop" command to monitor.
======== libvirt debug log ======
14:53:30.826: 21155: debug : qemuHandleMonitorEOF:739 : Received EOF on 0x7f4014002760 'virtlab_test'
14:53:30.826: 21155: debug : qemudShutdownVMDaemon:3406 : Shutting down VM 'virtlab_test' pid=22642 migrated=0
14:53:30.826: 21160: debug : qemuMonitorJSONCommandWithFd:243 : cannot send monitor command '{"execute":"stop"}': Connection reset by peer
======== libvirt Python exception ======
libvir: QEMU error : cannot resolve symlink /tmp/virtlab_test: No such file or directory
Traceback (most recent call last):
File "libvirt-test-api.py", line 304, in <module>
libvirt_test_api.run()
File "libvirt-test-api.py", line 168, in run
ret = i()
File "/usr/local/staf/test/RHEL6/libvirt-test-API/generator.py", line 82, in __call__
retflag = self.generator()
File "/usr/local/staf/test/RHEL6/libvirt-test-API/generator.py", line 130, in generator
ret = self.cases_func_ref_dict[case_ref_name](case_params)
File "/usr/local/staf/test/RHEL6/libvirt-test-API/repos/Python/domain/save.py", line 122, in save
domobj.save(guestname, filepath)
File "/usr/local/staf/test/RHEL6/libvirt-test-API/lib/Python/domainAPI.py", line 213, in save
retval = dom_obj.save(to)
File "/usr/lib64/python2.6/site-packages/libvirt.py", line 619, in save
if ret == -1: raise libvirtError ('virDomainSave() failed', dom=self)
libvirt.libvirtError: cannot resolve symlink /tmp/virtlab_test: No such file or directory
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
libvirt should only try to restore the security lable when the saving is successful.
Additional info:
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0596.html
Description of problem: E.g. When you use libvirt Python binding to save a domain, if the domain saving fails on send "stop" command to monitor. ======== libvirt debug log ====== 14:53:30.826: 21155: debug : qemuHandleMonitorEOF:739 : Received EOF on 0x7f4014002760 'virtlab_test' 14:53:30.826: 21155: debug : qemudShutdownVMDaemon:3406 : Shutting down VM 'virtlab_test' pid=22642 migrated=0 14:53:30.826: 21160: debug : qemuMonitorJSONCommandWithFd:243 : cannot send monitor command '{"execute":"stop"}': Connection reset by peer ======== libvirt Python exception ====== libvir: QEMU error : cannot resolve symlink /tmp/virtlab_test: No such file or directory Traceback (most recent call last): File "libvirt-test-api.py", line 304, in <module> libvirt_test_api.run() File "libvirt-test-api.py", line 168, in run ret = i() File "/usr/local/staf/test/RHEL6/libvirt-test-API/generator.py", line 82, in __call__ retflag = self.generator() File "/usr/local/staf/test/RHEL6/libvirt-test-API/generator.py", line 130, in generator ret = self.cases_func_ref_dict[case_ref_name](case_params) File "/usr/local/staf/test/RHEL6/libvirt-test-API/repos/Python/domain/save.py", line 122, in save domobj.save(guestname, filepath) File "/usr/local/staf/test/RHEL6/libvirt-test-API/lib/Python/domainAPI.py", line 213, in save retval = dom_obj.save(to) File "/usr/lib64/python2.6/site-packages/libvirt.py", line 619, in save if ret == -1: raise libvirtError ('virDomainSave() failed', dom=self) libvirt.libvirtError: cannot resolve symlink /tmp/virtlab_test: No such file or directory Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: libvirt should only try to restore the security lable when the saving is successful. Additional info: