Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2034570

Summary: ovirt-engine-rename points qemu-cert.template at ca-certificate resource
Product: [oVirt] ovirt-engine Reporter: Yedidyah Bar David <didi>
Component: Tools.RenameAssignee: Yedidyah Bar David <didi>
Status: CLOSED DUPLICATE QA Contact: meital avital <mavital>
Severity: medium Docs Contact:
Priority: unspecified    
Version: ---CC: bugs
Target Milestone: ovirt-4.5.2Flags: pm-rhel: ovirt-4.5?
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-17 06:11:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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 ***