Open benluddy opened 3 years ago
I've seen issues where locally the TearDown
chokes if the test is using a unique namespace, versus the default testNamespace
, which causes OLM to attempt to delete resources in the testNamespace
that do not exist.
For example the limits installed resources if the scoped serviceaccount has no permissions
test does everything in a standalone namespace not to interfere with the operatorgroup of the testNamespace
-- running this locally triggers cleanup to fail even though the test passes
Observed in https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/operator-framework_operator-lifecycle-manager/1972/pull-ci-operator-framework-operator-lifecycle-manager-master-e2e-aws-olm/1354184521808875520#1:build-log.txt%3A3814 and reproducible on a local kind cluster after several attempts. The resulting cluster pollution appears to cause some subsequent specs to fail.