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 1977520[details]
libvirtd log
Description of problem:
When deploying a VM with virt-install, the command hangs, not even being able to be stopped with ^C. The only way to make the command work again is to restart libvirtd service, but this is still an issue.
It has been seen in virt-install debug mode, that it hangs in "Requesting libvirt URI default"
On the other hand, the status of libvirtd service when hang, shows
libvirtd[52740]: cannot parse process status data
More details attached in the log.
Version-Release number of selected component (if applicable):
RHEL 9.3 compose RHEL-9.3.0-20230725.27
Date: 2023-07-25
osbuild-90-1.el9.noarch.rpm
osbuild-composer-85-1.el9.x86_64.rpm
weldr-client-35.9-1.el9.x86_64.rpm
KERNEL: 5.14.0-344.el9.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Deploy RHEL-9.3 VM in Openstack
2. git clone https://github.com/virt-s1/rhel-edge.git
3. ./ostree.sh
Actual results:
virt-install hangs and VM deployment fails due to timeout.
Expected results:
virt-install being successful to deploy VM
Additional info:
At that time, command "sudo virsh list --all" hangs as well. But libvirtd.service is active.
Restarting libvirtd service will resolve.
systemd and libvirt version:
systemd-252-16.el9.x86_64
libvirt-daemon-kvm-9.3.0-2.el9.x86_64
libvirt-daemon-9.3.0-2.el9.x86_64
I think it is the same issue as https://bugzilla.redhat.com/show_bug.cgi?id=2213660
The buggy commit for systems is: ff32060f2ed37b68dc26256b05e2e69013b0ecfe
core/service: when resetting PID also reset known flag
And systemd-252-16.el9.x86_64 contains this buggy commit:
➜ ~ rpm -q --changelog systemd-252-16.el9.x86_64 |grep 'core/service: when resetting PID also reset known flag'
- core/service: when resetting PID also reset known flag (#2210237)
(In reply to Han Han from comment #5)
> I think it is the same issue as
> https://bugzilla.redhat.com/show_bug.cgi?id=2213660
> The buggy commit for systems is: ff32060f2ed37b68dc26256b05e2e69013b0ecfe
> core/service: when resetting PID also reset known flag
>
> And systemd-252-16.el9.x86_64 contains this buggy commit:
> ➜ ~ rpm -q --changelog systemd-252-16.el9.x86_64 |grep 'core/service: when
> resetting PID also reset known flag'
> - core/service: when resetting PID also reset known flag (#2210237)
Yes, I've come to the same conclusion. There's another duplicate of this filed with libvirt just now.
Also hitting the same issue with CentOS 9-stream in OpenStack Upstream CI https://bugs.launchpad.net/neutron/+bug/2029335, would be good to get the revert patch included in systemd rpm to clear this issue.
Comment 11Frantisek Sumsal
2023-08-04 08:26:45 UTC
*** Bug 2229106 has been marked as a duplicate of this bug. ***
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 (systemd 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-2023:6640