Bug 2088515 - Run_after of certificate_requests in modular libvirt does not reload virtproxyd service
Summary: Run_after of certificate_requests in modular libvirt does not reload virtprox...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 17.0 (Wallaby)
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: ---
Assignee: Bogdan Dobrelya
QA Contact: Joe H. Rahme
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-19 15:35 UTC by Bogdan Dobrelya
Modified: 2023-08-16 01:11 UTC (History)
2 users (show)

Fixed In Version: openstack-tripleo-heat-templates-14.3.1-1.20220920001118.2b27b46.el9ost
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-16 01:11:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 846936 0 None NEW Fix run_after of certs_requests in modular libvirt 2022-06-21 11:39:25 UTC
Red Hat Issue Tracker OSP-15317 0 None None None 2022-05-19 15:56:06 UTC
Red Hat Product Errata RHEA-2023:4577 0 None None None 2023-08-16 01:11:50 UTC

Description Bogdan Dobrelya 2022-05-19 15:35:24 UTC 
Description of problem:

When changing the /etc/pki/qemu certs, there is no need to restart/reload any (modular libvirt) service.
Those certs are either loaded when QEMU VM is booted, or dynamically loaded into QEMU when a live migration takes place.

For the libvirt certs in /etc/pki/libvirt though, we need to either restart  'libvirtd.service' (monolithic world) or restart 'virtproxyd.service' (modular world). No need to restart 'virtqemud.service in modular world.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Yaniv Kaul 2022-06-21 08:29:47 UTC 
Upstream patch seem to have been merged. What's the next step? (should the BZ still be in NEW state?)
Comment 3 Bogdan Dobrelya 2022-06-23 13:57:41 UTC 
Pushing this out of 17.0 for 17.1
Comment 16 errata-xmlrpc 2023-08-16 01:11:11 UTC 
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 (Release of components for Red Hat OpenStack Platform 17.1 (Wallaby)), 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/RHEA-2023:4577
Note You need to log in before you can comment on or make changes to this bug.