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.
Deadline for the next batch update is december 7. I don't think this is going to make that.
Patch is not reviewed yet and QE is already pushing to move the errata to REL_PREP.
Tomas -
The z-stream processing for this bug was not able to make the deadline needed for QE testing on the RHEL-AV 8.3.0.z errata, so it will not be in Batch1 (GA 15-Dec).
It is queued up for Batch2 (GA 16-Feb) and should have all the downstream reviews by then.
Placing the needinfo mainly so you're aware and can provide feedback if something was really needed sooner for some customer specific case.
Comment 4Tomáš Golembiovský
2020-12-03 10:04:52 UTC
Reproduce with version qemu-kvm-4.2.0-29.module+el8.3.0+7212+401047e6.x86_64
Steps to Reproduce:
1.Boot rhel830 guest successfully.
2.Configure log persistence in guest:
[root@ vm-73-139~]# mkdir /var/log/journal
[root@ vm-73-139~]# chgrp systemd-journal /var/log/journal
[root@ vm-73-139~]# chmod g+s /var/log/journal
[root@ vm-73-139~]# systemctl restart systemd-journald
3.Send following command in above socket connection in the host side to shutdown the guest:
[root@dell-per440-06 ~]# nc -U /tmp/qga.sock
{"execute":"guest-ping"}
{"return": {}}
{ "execute":"guest-shutdown","arguments":{"mode":"powerdown"}}
4.Check qga.service status after guest reboot.
[root@ vm-73-139~]# journalctl -e | grep -6 -i "ERROR"
Actual result:
Nov 22 21:12:48 localhost.localdomain systemd[1]: Started QEMU Guest Agent.
Nov 22 21:13:32 localhost.localdomain qemu-ga[719]: info: guest-shutdown called, mode: powerdown
Nov 22 21:13:33 localhost.localdomain qemu-ga[719]: **
Nov 22 21:13:33 localhost.localdomain qemu-ga[719]: ERROR:qga/main.c:532:send_response: assertion failed: (rsp && s->channel)
Nov 22 21:13:33 localhost.localdomain systemd[1]: Stopping QEMU Guest Agent...
Nov 22 21:13:33 localhost.localdomain systemd[1]: qemu-guest-agent.service: Main process exited, code=dumped, status=6/ABRT
Nov 22 21:13:33 localhost.localdomain systemd[1]: qemu-guest-agent.service: Failed with result 'core-dump'.
Nov 22 21:13:33 localhost.localdomain systemd[1]: Stopped QEMU Guest Agent.
Expected result:
There is no error that qga.service abort after shutdown.
Verified with version qemu-kvm-4.2.0-34.module+el8.3.0+9094+80c20d97.2
Steps to Reproduce like above,but boot up rhel840 guest instead.
Actual result:
There is no error that qga.service abort after shutdown.
Expected result
There is no error that qga.service abort after shutdown.
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 (virt:rhel bug fix 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-2021:0542