https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-4.2/104 ``` [Feature:OpenShiftAuthorization][Serial] authorization TestAuthorizationResourceAccessReview should succeed [Suite:openshift/conformance/serial] expand_less 32s fail [github.com/onsi/ginkgo/internal/leafnodes/runner.go:109]: who can view deploymentconfigs in hammer by harold: who can get deploymentconfigs (in the current namespace): ```
support-operator is not yet installed in OCP, the e2e test is overly specific and doesn't tolerate support-operator's roles Fix with https://gitlab.cee.redhat.com/openshift-art/ocp-build-data/merge_requests/176 and https://projects.engineering.redhat.com/browse/RCMAUTO-800
Talked with David, the test may be too aggressive if we have multiple different sets of operators installed on a cluster (the test will fail if someone adds an operator with cluster reader). We will probably make the e2e more flexible as well.
I haven't seen the DC failure in recent CI runs (2w), so closing. I'm not sure what is Clayton referring to :-)
I get the error again https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-sdn-multitenant-4.2/125
Verified. This case will not failed now, https://testgrid.k8s.io/redhat-openshift-release-blocking#redhat-release-openshift-ocp-installer-e2e-aws-serial-4.2
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-2019:2922