-
Bug
-
Resolution: Done
-
Blocker
-
quay-v3.4.0
-
False
-
False
-
Undefined
-
Description:
This is an issue found when use new Quay TNG Operator to deploy Quay, after created quay CR, Quay APP POD is stuck in creating status, checked OCP Console POD events, get error message "MountVolume.SetUp failed for volume "configvolume" : secret "quaydemo-quay-config-secret-7ct62b6bcf" not found", and checked all secret ,found Quay TNG operator didn't create required quy-config-secret as required.
Quay Catalogsoure Image:
oc get pod quay-operator-788hj -n openshift-marketplace -o json | jq '.status.containerStatuses[0].imageID' "quay.io/quay/quay-operator-catalog@sha256:6104b66579f04aade6a7eeecbf52cf2b17a5445260ce01f7d7493c7d5eddc00d"
Quay Operator image:
oc get pod quay-operator-76bcc65784-rmc57 -o json | jq '.spec.containers[0].image' "quay.io/quay/quay-operator@sha256:dc1ef4d84795d8c35c4f0c01135154a7fb51f8876c583a932b1dc7ae8f492fad"
OCP Version: 4.5.0
oc get pod NAME READY STATUS RESTARTS AGE quay-operator-76bcc65784-rmc57 1/1 Running 0 3h21m quaydemo-quay-app-upgrade-5c984cccc8-6b28l 0/1 ContainerCreating 0 3h14m quaydemo-quay-config-editor-684c7b86dd-ptz4c 0/1 ContainerCreating 0 3h14m oc get secret NAME TYPE DATA AGE builder-dockercfg-5qn5j kubernetes.io/dockercfg 1 3h35m builder-token-466n2 kubernetes.io/service-account-token 4 3h35m builder-token-rcmdc kubernetes.io/service-account-token 4 3h35m default-dockercfg-2r4pj kubernetes.io/dockercfg 1 3h35m default-token-4k7m5 kubernetes.io/service-account-token 4 3h35m default-token-pfb2k kubernetes.io/service-account-token 4 3h35m deployer-dockercfg-5qcnc kubernetes.io/dockercfg 1 3h35m deployer-token-dmgts kubernetes.io/service-account-token 4 3h35m deployer-token-sjgrk kubernetes.io/service-account-token 4 3h35m lzha-pull-secret kubernetes.io/dockerconfigjson 1 3h32m quay-operator-dockercfg-47zmc kubernetes.io/dockercfg 1 3h20m quay-operator-token-bx6l8 kubernetes.io/service-account-token 4 3h20m quay-operator-token-z4n7z kubernetes.io/service-account-token 4 3h20m quaydemo-config-bundle-hl6vl Opaque 1 3h20m quaydemo-config-bundle-pvvr8 Opaque 1 3h14m quaydemo-quay-config-editor-credentials Opaque 1 3h14m
Quay CR:
apiVersion: quay.redhat.com/v1 kind: QuayRegistry metadata: name: quaydemo
Noobaa.yaml:
apiVersion: noobaa.io/v1alpha1 kind: NooBaa metadata: name: noobaa namespace: openshift-storage spec: dbResources: requests: cpu: '0.1' memory: 1Gi coreResources: requests: cpu: '0.1' memory: 1Gi
Steps:
- Login OCP Console
- Create new OCP Namespace and deploy Quay TNG Operator
- Deploy RHOCS Operator
- Run "create -n openshift-storage -f noobaa.yml"
- Create Quay CR with "create -n quay0340 -f quay.yaml"
- Check POD status created by Quay CR above
Expected Results:
All POD created by Quay CR come to be ready status
Actual Results:
Quay APP POD was stuck in ContainerCreating status.
