Bug 1789291

Summary:	Missing ca.pem recreation question should be part of PKI section
Product:	[oVirt] ovirt-engine	Reporter:	Petr Matyáš <pmatyas>
Component:	Setup.Core	Assignee:	Yedidyah Bar David <didi>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Petr Matyáš <pmatyas>
Severity:	medium	Docs Contact:
Priority:	low
Version:	4.4.0	CC:	bugs, dfodor
Target Milestone:	ovirt-4.4.0	Flags:	pm-rhel: ovirt-4.4+
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:	2020-05-20 20:01:22 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:
Bug Depends On:	1700021
Bug Blocks:

Description Petr Matyáš 2020-01-09 09:35:51 UTC

Description of problem:
When you move ca.pem elsewhere (or remove it) you get prompted during engine setup to recreate PKI files or restore from backup, however this question is posed only at the end of engine-setup and not during PKI section.

Version-Release number of selected component (if applicable):
ovirt-engine-4.4.0-0.13.master.el7.noarch

How reproducible:
always

Steps to Reproduce:
1. remove/move ca.pem
2. engine-setup
3.

Actual results:
PKI files recreation question is not part of PKI

Expected results:
it should be part of PKI section in setup

Additional info:

Comment 1 RHV bug bot 2020-01-24 19:51:06 UTC

INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[Tag 'ovirt-engine-4.4.0' doesn't contain patch 'https://gerrit.ovirt.org/106205']
gitweb: https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=shortlog;h=refs/tags/ovirt-engine-4.4.0

For more info please contact: infra

Comment 2 Petr Matyáš 2020-03-20 11:31:32 UTC

Verified on ovirt-engine-4.4.0-0.25.master.el8ev.noarch

Comment 3 Sandro Bonazzola 2020-05-20 20:01:22 UTC

This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.

Since the problem described in this bug report should be
resolved in oVirt 4.4.0 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.