-
Bug
-
Resolution: Done
-
Blocker
-
quay-v3.6.0
-
False
-
False
-
Quay Enterprise
-
Description of problem:
Quay operator failed to uprade from 3.4 to 3.6, 3.6 operator is stuck in pending status
Version-Release number of selected component (if applicable):
quay-operator-bundle-container-v3.6.0-40
- Index image v4.5: registry-proxy.engineering.redhat.com/rh-osbs/iib:113826
- Index image v4.6: registry-proxy.engineering.redhat.com/rh-osbs/iib:113828
- Index image v4.7: registry-proxy.engineering.redhat.com/rh-osbs/iib:113831
- Index image v4.8: registry-proxy.engineering.redhat.com/rh-osbs/iib:113834
- Index image v4.9: registry-proxy.engineering.redhat.com/rh-osbs/iib:113837
How reproducible:
always
Steps to Reproduce:
1. Install 3.4 operator, create quayregistry CR
2. Upgrade operator from 3.4 to 3.6 via OLM
3. Check 3.6 operator status
Actual results:
failed, operator is stuck in pending status
logs in olm pod:
time="2021-09-25T05:41:09Z" level=info msg="checking quay-operator.v3.5.6"
time="2021-09-25T05:41:09Z" level=info msg="checking container-security-operator.v3.6.0"
time="2021-09-25T05:41:09Z" level=info msg="checking quay-operator.v3.6.0"
time="2021-09-25T05:41:09Z" level=info msg="quay-operator.v3.5.6 replaced by quay-operator.v3.6.0"
time="2021-09-25T05:41:09Z" level=info msg="requirements were not met" csv=quay-operator.v3.6.0 id=MujYz namespace=openshift-operators phase=Pending
time="2021-09-25T05:41:09Z" level=info msg="checking quay-operator.v3.6.0"
time="2021-09-25T05:41:09Z" level=info msg="quay-operator.v3.5.6 replaced by quay-operator.v3.6.0"
time="2021-09-25T05:41:09Z" level=info msg="couldn't ensure RBAC in target namespaces" csv=quay-operator.v3.6.0 error="no owned roles found" id=xvFfP namespace=openshift-operators phase=Pending
E0925 05:41:09.199266 1 queueinformer_operator.go:290] sync {"update" "openshift-operators/quay-operator.v3.6.0"} failed: no owned roles found
time="2021-09-25T05:41:09Z" level=info msg="checking quay-bridge-operator.v3.6.0"
time="2021-09-25T05:41:09Z" level=info msg="checking quay-operator.v3.5.6"
time="2021-09-25T05:41:09Z" level=info msg="checking container-security-operator.v3.6.0"
time="2021-09-25T05:41:09Z" level=info msg="checking quay-operator.v3.6.0"
time="2021-09-25T05:41:09Z" level=info msg="quay-operator.v3.5.6 replaced by quay-operator.v3.6.0"
time="2021-09-25T05:41:09Z" level=info msg="requirements were not met" csv=quay-operator.v3.6.0 id=3cYI3 namespace=openshift-operators phase=Pending
time="2021-09-25T05:41:09Z" level=info msg="checking quay-bridge-operator.v3.6.0"
time="2021-09-25T05:41:09Z" level=info msg="checking quay-operator.v3.5.6"
time="2021-09-25T05:41:09Z" level=info msg="checking container-security-operator.v3.6.0"
time="2021-09-25T05:41:09Z" level=info msg="checking quay-operator.v3.6.0"
time="2021-09-25T05:41:09Z" level=info msg="quay-operator.v3.5.6 replaced by quay-operator.v3.6.0"
Expected results:
upgrade success
Additional info:
This is a regression issue, because this issue does not exist in quay-quay-operator-bundle:v3.6.0-30
- clones
-
PROJQUAY-2584 Quay operator failed to upgrade from 3.5 to 3.6
-
- Closed
-