Bug 2034570 - ovirt-engine-rename points qemu-cert.template at ca-certificate resource
Summary: ovirt-engine-rename points qemu-cert.template at ca-certificate resource
Keywords:
Status: CLOSED DUPLICATE of bug 1912067
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Tools.Rename
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.5.2
: ---
Assignee: Yedidyah Bar David
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-21 10:44 UTC by Yedidyah Bar David
Modified: 2022-06-23 05:58 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-17 06:11:55 UTC
oVirt Team: Integration
Embargoed:
pm-rhel: ovirt-4.5?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-44389 0 None None None 2021-12-21 10:45:36 UTC

Description Yedidyah Bar David 2021-12-21 10:44:33 UTC
Description of problem:

/etc/pki/ovirt-engine/qemu-cert.template is rewritten with authorityInfoAccess pointing at ca-certificate instead of qemu-ca-certificate resource. This affects future qemu-ca certificates that would be generated using this template. Not sure what actual significance this might have. This is more-or-less the "opposite" of bug 1875386, but for rename.

Version-Release number of selected component (if applicable):
Current master, probably since early 4.4 (bug 1739557? bug 1875386?).

How reproducible:
Always

Steps to Reproduce:
1. Set up an engine
2. Use ovirt-engine-rename with some new name
3. grep ca-certificate /etc/pki/ovirt-engine/*.template
4. 

Actual results:
All files point at pki-resource?resource=ca-certificate

Expected results:
cert.template points at pki-resource?resource=ca-certificate
qemu-cert.template points at pki-resource?resource=qemu-ca-certificate

Additional info:

Comment 1 Yedidyah Bar David 2022-05-17 06:11:55 UTC

*** This bug has been marked as a duplicate of bug 1912067 ***


Note You need to log in before you can comment on or make changes to this bug.