Bug 1791004 - Change the next empty encryption key's name for encryption e2e test
Summary: Change the next empty encryption key's name for encryption e2e test
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Test Infrastructure
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.4.0
Assignee: Lukasz Szaszkiewicz
QA Contact: Xingxing Xia
URL:
Whiteboard:
Depends On:
Blocks: 1795693
TreeView+ depends on / blocked
 
Reported: 2020-01-14 16:40 UTC by Lukasz Szaszkiewicz
Modified: 2020-05-04 11:24 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1795693 (view as bug list)
Environment:
Last Closed: 2020-05-04 11:24:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:0581 0 None None None 2020-05-04 11:24:40 UTC

Description Lukasz Szaszkiewicz 2020-01-14 16:40:38 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:10:57 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-28 16:35:37 UTC
@Xingxing please move it to close as this is a non-customer facing issue.

Comment 6 Lukasz Szaszkiewicz 2020-01-30 08:36:23 UTC
@Xingxing still can't merge https://github.com/openshift/cluster-openshift-apiserver-operator/pull/298, the bot says that the BZ is in an invalid state: "expected dependent Bugzilla bug 1791004 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is CLOSED (NOTABUG) instead"
@Xingxing could you move it to one of the valid states?

Comment 10 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


Note You need to log in before you can comment on or make changes to this bug.