Open akihikokuroda opened 2 years ago
Here is the olm-operator log around the the test.
2022-01-18T20:20:22.749311127Z stderr F time="2022-01-18T20:20:22Z" level=debug msg="No matched TargetNamespaces are found for given selector: labels.internalSelector{labels.Requirement{key:\"foo\", operator:\"=\", strValues:[]string{\"bar\"}}}\n"
2022-01-18T20:20:22.749416128Z stderr F time="2022-01-18T20:20:22Z" level=debug msg="updated target namespaces" namespace=namespace-a-2zwcx operatorGroup=e2e-operator-group-qwhlj targetNamespaces="[]"
2022-01-18T20:20:22.74954053Z stderr F time="2022-01-18T20:20:22Z" level=debug msg="check that operatorgroup has updated CSV anotations" namespace=namespace-a-2zwcx operatorGroup=e2e-operator-group-qwhlj
2022-01-18T20:20:22.752788265Z stderr F time="2022-01-18T20:20:22Z" level=debug msg="OperatorGroup CSV annotation completed" namespace=namespace-a-2zwcx operatorGroup=e2e-operator-group-qwhlj
2022-01-18T20:20:22.770774163Z stderr F time="2022-01-18T20:20:22Z" level=debug msg="operatorgroup clusterroles ensured" namespace=namespace-a-2zwcx operatorGroup=e2e-operator-group-qwhlj
There is no error but this message No matched TargetNamespaces are found for given selector
. The syncOperatorGroups
didn't see the labels. It is using the namespace lister to get the list of the namespaces. I assume this is cache timing issue.
Bug Report
e2e - "OLM applies labels to Namespaces that are associated with an OperatorGroup" failed. https://github.com/operator-framework/operator-lifecycle-manager/runs/4858730278?check_suite_focus=true#step:4:2223
What did you do? Check CI build failure What did you expect to see? No error What did you see instead? Under which circumstances? e2e test failure above
Environment
Possible Solution
Additional context Add any other context about the problem here.