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.
This bug was initially created as a copy of Bug #1792723
I am copying this bug because:
This bug appeared with:
libvirt-4.5.0-36.el7.x86_64
Description of problem:
Domain set time does not releases the lock which causes getting domain time failed.
Version-Release number of selected component (if applicable):
libvirt-6.0.0-1.module+el8.2.0+5453+31b2b136.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Start guest and get domain time and set domain time
# virsh domtime test
Time: 1579436433
# virsh domtime test --time 1000000000
2. Get domain time again, but get hung for 30 seconds and finally timeout.
# date;virsh domtime test;date
Sun Jan 19 07:23:01 EST 2020
error: Timed out during operation: cannot acquire state change lock (held by agent=remoteDispatchDomainSetTime)
Sun Jan 19 07:23:31 EST 2020
Actual results:
See above.
Expected results:
virsh command returns OK.
Additional info:
This issue was caused by a fix for CVE-2019-20485 included in
libvirt-4.5.0-35.el7. The regression is already fixed upstream by:
commit d61f95cf6a6fbd564e104c168d325581acd9cd8d
Author: Ján Tomko <jtomko>
CommitDate: 2020-01-20 07:55:48 +0100
qemu: end the agent job in qemuDomainSetTimeAgent
This function grabs an agent job but ends a monitor job.
End the agent job instead.
https://bugzilla.redhat.com/show_bug.cgi?id=1792723
Signed-off-by: Ján Tomko <jtomko>
Reported-by: Dan Zheng <dzheng>
Fixes: e005c95f56fee9ed780be7f8db103d690bd34cbd
git describe: v6.0.0-67-gd61f95cf6a
Verify this bug with:
libvirt-4.5.0-36.el7_7.9.1.x86_64
qemu-guest-agent-2.12.0-3.el7.x86_64
For the verification steps, please refer to Bug #1792723
As the testing result matches with the expected result, mark the bug as verified
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 (libvirt bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2020:4070