Open timflannagan opened 2 years ago
Poking around that linked action's container logs, it's not immediately clear why that test case failed as we don't collect any additional test fixtures for debugging (e.g. configmaps in the operators namespace in this case). Looking at the test code, it's possible we have an issue with test pollution in the installplan e2e suite as well, where we create resources in shared namespace, typically in the operators
namespace. This can lead to poor testing assumptions and failed assertions.
Ran into this error in https://github.com/operator-framework/operator-lifecycle-manager/pull/2438.
This https://github.com/operator-framework/operator-lifecycle-manager/pull/2444 may fix this issue.
The "Catalog represents a store of bundles which OLM can use to install Operators [It] config map update triggers registry pod rollout" test case occasionally flakes. Link to an action run that exhibits this failing test: https://github.com/operator-framework/operator-lifecycle-manager/runs/4154202639?check_suite_focus=true.