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

Bug 1851921

Summary:	Disable activation of the host while Enroll certificate flow is still in progress [RHV clone - 4.3.11]
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	RHV bug bot <rhv-bugzilla-bot>
Component:	ovirt-engine	Assignee:	Martin Perina <mperina>
Status:	CLOSED ERRATA	QA Contact:	Petr Matyáš <pmatyas>
Severity:	medium	Docs Contact:
Priority:	high
Version:	4.3.7	CC:	cshao, gchakkar, kmashalk, kshukla, mjankula, mkalinin, mperina, pelauter, yturgema
Target Milestone:	ovirt-4.3.11	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:	1801709	Environment:
Last Closed:	2020-09-30 10:07:26 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1801709
Bug Blocks:

Comment 1 RHV bug bot 2020-06-29 12:53:21 UTC

This is not a bug, this is new requirement which we were need to put on host certificates to ensure possibility of future upgrade to EL8 based hosts. Details are described in BZ1763109.

So you need to put affected hosts to Maintenance, perform Renroll Certificate and Activate them afterwards.

Anyway it also needs to be mentioned that this operation can be postponed and planned accordingly, this is only warning, but host is fully functional even with certificate without SAN field.

(Originally by Martin Perina)

Comment 19 Petr Matyáš 2020-07-13 10:20:54 UTC

Verified on ovirt-engine-4.3.11.2-0.1.el7.noarch

Comment 25 errata-xmlrpc 2020-09-30 10:07:26 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 (Red Hat Virtualization Engine security, bug fix 4.3.11), 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/RHBA-2020:4112