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

Bug 1791023

Summary:	Change the next empty encryption key's name for encryption e2e test
Product:	OpenShift Container Platform	Reporter:	Lukasz Szaszkiewicz <lszaszki>
Component:	Test Infrastructure	Assignee:	Lukasz Szaszkiewicz <lszaszki>
Status:	CLOSED ERRATA	QA Contact:	Xingxing Xia <xxia>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.3.0	CC:	aos-bugs, mfojtik, scuppett, sttts
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	1795701 (view as bug list)		Environment:
Last Closed:	2020-05-04 11:24:10 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1795701

Description Lukasz Szaszkiewicz 2020-01-14 17:27:28 UTC

We need to backport an important fix that fixes the encryption e2e tests. Without it, the tests could get into a state in which they expect the previous key to have "no previous key" name instead of an empty string. As it happened in https://prow.svc.ci.openshift.org/pr-history/?org=openshift&repo=cluster-openshift-apiserver-operator&pr=288

The following fix [1] needs to be applied to cluster-openshift-apiserver-operator

[1] https://github.com/openshift/library-go/pull/665

Comment 2 Stephen Cuppett 2020-01-17 18:06:12 UTC

Setting target release to the active development branch (4.4). For fixes, if any, which require backport to prior versions, clones of this BZ will be created.

Comment 3 Lukasz Szaszkiewicz 2020-01-30 08:39:40 UTC

@Xingxing please close it as this is a non-customer facing issue. I want to merge https://github.com/openshift/cluster-kube-apiserver-operator/pull/717
Please note that you need to move it to a valid state (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA).

Comment 5 Xingxing Xia 2020-02-06 10:44:52 UTC

Thx for above info. Moving forward like bug 1791004#c8

Comment 7 errata-xmlrpc 2020-05-04 11:24:10 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, 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:0581