Bug 2088515

Summary:	Run_after of certificate_requests in modular libvirt does not reload virtproxyd service
Product:	Red Hat OpenStack	Reporter:	Bogdan Dobrelya <bdobreli>
Component:	openstack-tripleo-heat-templates	Assignee:	Bogdan Dobrelya <bdobreli>
Status:	CLOSED ERRATA	QA Contact:	Joe H. Rahme <jhakimra>
Severity:	medium	Docs Contact:
Priority:	low
Version:	17.0 (Wallaby)	CC:	alifshit, mburns
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-14.3.1-1.20220920001118.2b27b46.el9ost	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-08-16 01:11:11 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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