-
Bug
-
Resolution: Done
-
Blocker
-
quay-v3.4.0
-
False
-
False
-
Quay Enterprise
-
Undefined
-
Description of problem:
Quay operator pod crashed after create quayregistry CR
Version-Release number of selected component (if applicable):
- brew.registry.redhat.io/rh-osbs/quay-quay-quay-operator-container@sha256:d64862d9da324bf5ac00170d958224e25cca886a1b425d74ac8f5a7d0dbce861 (v3.4.0-33)
- brew.registry.redhat.io/rh-osbs/quay-quay-operator-bundle:v3.4.0-11
- Index image v4.6: brew.registry.redhat.io/rh-osbs/iib:22581
How reproducible:
Always
Steps to Reproduce:
1. Install quay operator and OCS operator
2. Create noobaa resource
'''
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
'''
3.Create quayregistry resource
'''
apiVersion: quay.redhat.com/v1
kind: QuayRegistry
metadata:
name: quay-test
'''
4. Check operator pod and quayregistry status
Actual results:
Quay operator crashed
$ oc get po -n openshift-operators -w
NAME READY STATUS RESTARTS AGE
quay-operator-67459d447b-488vk 0/1 CrashLoopBackOff 6 41m
Expected results:
quayregistry is created, deploy quay successfully
Additional info:
Noobaa is ready
$ oc get noobaa -n openshift-storage
NAME MGMT-ENDPOINTS S3-ENDPOINTS IMAGE PHASE AGE
noobaa ["https://10.0.161.124:31844"] ["https://10.0.161.124:31963"] registry.redhat.io/ocs4/mcg-core-rhel8@sha256:140ea8093d00ccba882b26d10b2e45ba8e108ee16b35e68d5050025747c3caf8 Ready 5m10s