Bug 1291789 - ovirt-engine-rename tool uses hard-coded ca.crt
Summary: ovirt-engine-rename tool uses hard-coded ca.crt
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Tools.Rename
Version: 3.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.3.2
: 4.3.2.1
Assignee: Asaf Rachmani
QA Contact: Petr Matyáš
URL:
Whiteboard:
: 1365840 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-15 15:28 UTC by Yedidyah Bar David
Modified: 2019-04-28 09:47 UTC (History)
7 users (show)

Fixed In Version: ovirt-engine-4.3.2.1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-26 07:20:52 UTC
oVirt Team: Integration
Embargoed:
rule-engine: ovirt-4.3+
lleistne: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1370904 0 medium CLOSED Engine's rename tool does not re-enroll PKI for engine services 2022-02-25 08:31:30 UTC
oVirt gerrit 98426 0 master MERGED packaging: setup: rename: Set authorityInfoAccess to the correct value 2020-08-27 19:43:35 UTC

Internal Links: 1370904

Description Yedidyah Bar David 2015-12-15 15:28:52 UTC 
Description of problem:

Should use ENGINE_PKI_CA_URI like the setup code. See also bug 961677.
Comment 1 Yedidyah Bar David 2015-12-15 15:34:50 UTC 
engine-setup creates cert.template with:

authorityInfoAccess = caIssuers;URI:http://FQDN:80/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA

rename changes that to:

authorityInfoAccess = caIssuers;URI:http://NEW_FQDN:80/ca.crt
Comment 2 Sandro Bonazzola 2016-05-02 10:10:17 UTC 
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
Comment 3 Yaniv Lavi 2016-05-23 13:26:06 UTC 
oVirt 4.0 beta has been released, moving to RC milestone.
Comment 4 Yaniv Lavi 2016-05-23 13:26:37 UTC 
oVirt 4.0 beta has been released, moving to RC milestone.
Comment 5 Yedidyah Bar David 2017-02-14 13:02:09 UTC 
*** Bug 1365840 has been marked as a duplicate of this bug. ***
Comment 6 Yaniv Kaul 2017-09-04 14:04:10 UTC 
close-deferred? or delay to 4.3?
Comment 7 Yedidyah Bar David 2017-09-04 14:10:10 UTC 
OK for 4.3. I'd rather not close, it's a trivial fix.
Comment 8 Yaniv Lavi 2018-06-25 07:26:40 UTC 
Closing old bugs.
Please reopen if still relevant.
Patches are welcomed.
Comment 9 Yedidyah Bar David 2018-06-25 07:29:40 UTC 
Should be easy fix, might eventually be important - although I didn't run into real problems yet.
Comment 10 Sandro Bonazzola 2019-01-21 08:28:52 UTC 
re-targeting to 4.3.1 since this BZ has not been proposed as blocker for 4.3.0.
If you think this bug should block 4.3.0 please re-target and set blocker flag.
Comment 11 Sandro Bonazzola 2019-02-18 07:55:02 UTC 
Moving to 4.3.2 not being identified as blocker for 4.3.1.
Comment 12 Petr Matyáš 2019-03-21 10:18:36 UTC 
Verified on ovirt-engine-4.3.2.1-0.1.el7.noarch
Comment 13 Sandro Bonazzola 2019-03-26 07:20:52 UTC 
This bugzilla is included in oVirt 4.3.2 release, published on March 19th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.2 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.