+++ This bug was initially created as a clone of Bug #1829576 +++
Add an e2e test to validates that stale condition DefaultSecurityContextConstraintsUpgradeable is removed from the status block.
To make the release cut off, we validated manually and had to merge the corresponding PR without an e2e test.
Waiting for https://github.com/openshift/cluster-kube-apiserver-operator/pull/845 to be approved by the cherry-pick manager.
I accidentally set the target release to "4.4.0", setting it to "4.4.z".
Waiting for it to be cherry-picked.
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.4.0-0.nightly-2020-06-21-210301 True False 6h8m Cluster version is 4.4.0-0.nightly-2020-06-21-210301
Related test code can cover the fix:
$ git clone https://github.com/openshift/cluster-kube-apiserver-operator.git# or git pull if already cloned
$ cd cluster-kube-apiserver-operator/
$ git branch -a
$ git checkout remotes/origin/release-4.4
$ cd test/e2e
$ $ ls clean_stale_condition_test.go
$ go test -v -run TestRemoveStaleSCCUpgradeableCondition
=== RUN TestRemoveStaleSCCUpgradeableCondition
Found configuration for host https://api.ke22gcp41.qe.gcp.cluster.com:6443.
--- PASS: TestRemoveStaleSCCUpgradeableCondition (7.44s)
ok github.com/openshift/cluster-kube-apiserver-operator/test/e2e 7.461s
The test run passed as expected, move the bug verified.
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.