-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
quay-v3.16.0
-
Quality / Stability / Reliability
-
False
-
-
False
-
-
Description:
This is a serious bug but it seldom happen, when enable FEATURE_IMAGE_PULL_STATS, quayregstiry cr can't be provisioned
Quay: stable-3-16-v4-19
Steps:
- In config.yaml, add this:
FEATURE_IMAGE_PULL_STATS: true REDIS_FLUSH_INTERVAL_SECONDS: 30 PULL_METRICS_REDIS: host: quayregistry-quay-redis port: 6379 db: 1
2. then provision quay registry cr
Result:
Redis | Could not connect to Redis with values provided in PULL_METRICS_REDIS. Error: dial tcp: lookup quayregistry-quay-redis on 172.30.0.10:53: no such host | 🔴 |
% oc get pod
NAME READY STATUS RESTARTS AGE
example-registry-clair-app-5487645c96-kvzjf 1/1 Running 0 27m
example-registry-clair-app-5487645c96-nb57c 1/1 Running 4 (28m ago) 29m
example-registry-clair-postgres-759776d4d9-t7jpb 1/1 Running 0 28m
example-registry-quay-app-7bc44dbc48-jnlv8 0/1 CrashLoopBackOff 10 (80s ago) 27m
example-registry-quay-app-7bc44dbc48-z4ww4 0/1 CrashLoopBackOff 10 (20s ago) 26m
example-registry-quay-app-upgrade-6c849 0/1 Completed 3 29m
example-registry-quay-database-7f96fc7796-kb7jb 1/1 Running 0 28m
example-registry-quay-mirror-c7d5864b7-csdth 0/1 Init:CrashLoopBackOff 10 (28s ago) 26m
example-registry-quay-mirror-c7d5864b7-vvd56 0/1 Init:CrashLoopBackOff 10 (2m25s ago) 28m
example-registry-quay-redis-7466f7cc-gjwkn 1/1 Running 0 29m
quay-operator.v3.16.0-758dfcbd84-zwbwb 1/1 Running 0 29m
