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.
Yeah, this looks like something we need to address - currently libvirtd is restarted by a %post script, and we'll need todo the same for other daemons.
This was addressed in spec file updates in the 7.7.0 release upstream.
3315bc3ba8a9022c97b866a768914fb30592496a rpm: fix typo in post transaction scriptlet name
821414f0cdec77e6d8d11a189e02197238df918d rpm: add conditionals around post scripts
50eae3f8859c746aa474401b38902fa500f23fad rpm: handle enabling/disabling modular daemons post/postun-install
a97c2b14b22f6e7ea177f43ff9e6f7a7f071a53c rpm: macroize logic for enabling/disabling daemons post/postun-install
b8ef62554449ba8f38f3b265fd4751fa8d7bfc88 rpm: restart modular daemons on upgrade
c2eafaf7a30248d5ac9bc0557e727353bf8669e1 rpm: restart virtnwfilter/virnetworkd if configs change
b5e8db8f14ddc0bae0194c21fa9f1a748fb630b7 rpm: macroize logic for restarting daemons post-transaction
This will be addressed in the 7.7.0 rebase, assuming the RPM specfile contents are synced too.
Verified with
Test steps:
1.Active all the sub-daemons:
#for i in {1..100}; do for drv in qemu interface network nodedev nwfilter secret storage; do virsh connect ${drv}:///system; done; done
2.Open another terminal and get the pid of sub-daemons:
#for drv in qemu interface network nodedev nwfilter secret storage; do pidof virt${drv}d ; done
1557
2387
2408
2340
2536
2558
2618
3.Upgrade libvirt pkgs:
# yum -y upgrade libvirt*
4.Check the pid of sub-daemons and can see all the sub-daemons are restarted after upgrade:
# for drv in qemu interface network nodedev nwfilter secret storage; do pidof virt${drv}d ; done
9050
8974
8897
9008
8932
9084
9126
(In reply to yafu from comment #9)
> Verified with
>
> Test steps:
> 1.Active all the sub-daemons:
> #for i in {1..100}; do for drv in qemu interface network nodedev nwfilter
> secret storage; do virsh connect ${drv}:///system; done; done
>
> 2.Open another terminal and get the pid of sub-daemons:
> #for drv in qemu interface network nodedev nwfilter secret storage; do pidof
> virt${drv}d ; done
> 1557
> 2387
> 2408
> 2340
> 2536
> 2558
> 2618
>
> 3.Upgrade libvirt pkgs:
> # yum -y upgrade libvirt*
>
> 4.Check the pid of sub-daemons and can see all the sub-daemons are restarted
> after upgrade:
> # for drv in qemu interface network nodedev nwfilter secret storage; do
> pidof virt${drv}d ; done
> 9050
> 8974
> 8897
> 9008
> 8932
> 9084
> 9126
Verified with libvirt-7.8.0-1.el9.x86_64.
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 (new packages: libvirt), 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-2022:2390
Description of problem: split daemons not restart after upgrading libvirt pkgs Version-Release number of selected component (if applicable): libvirt-6.0.0-17.module+el8.2.0+6257+0d066c28.x86_64 How reproducible: 100% Steps to Reproduce: 1.Disable libvirtd and enable virtqemud service: #systemctl stop libvirtd.service #systemctl stop libvirtd{,-ro,-admin,-tcp,-tls}.socket #systemctl start virtqemud #systemctl start virtproxyd 2.rpm -q libvirt libvirt-6.0.0-15.el8.x86_64 3.# ll /run/libvirt/ total 0 ... srw-------. 1 root root 0 Apr 10 05:45 libvirt-admin-sock srw-rw-rw-. 1 root root 0 Apr 10 05:45 libvirt-sock srw-rw-rw-. 1 root root 0 Apr 10 05:45 libvirt-sock-ro srw-------. 1 root root 0 Apr 10 05:45 virtqemud-admin-sock srw-rw-rw-. 1 root root 0 Apr 10 05:45 virtqemud-sock srw-rw-rw-. 1 root root 0 Apr 10 05:45 virtqemud-sock-ro ... 4.Check virtqemud and virtproxyd process id: #pgrep virtqemud 97820 #pgrep virtproxyd 100628 5.Upgrade libvirt pkgs: #yum -y upgrade libvirt* libvirt-6.0.0-17.el8.x86_64 6.Check virtqemud and virtproxyd process id: #pgrep virtqemud 97820 # pgrep virtproxyd 100628 Actual results: split daemons not restart after upgrading libvirt pkgs Expected results: split daemons should restart after upgrading libvirt pkgs Additional info: