TomHutter
Mission Specialist
Mission Specialist
  • 422 Views

Guided Exercise: Deploying and Configuring Red Hat Quay - Pod central-quay-app CrashLoopBackOff

Jump to solution

Hello everybody,

I am trying to do the Guided Exercise: Deploying and Configuring Red Hat Quay. But i fail to complete step 3.3

oc get pods -n registry| grep central-quay-app | grep Running

First of all, the scaling for the deployment central-quay-app was set to 0 which I changed by:

oc scale deploy/central-quay-app --replicas=1

Now the pod central-quay-app-55f588fc48-jtkq7 is in state CrashLoopBackOff and the logs show:

| DistributedStorage | DISTRIBUTED_STORAGE_CONFIG.local_us.access_key is required | |
+ +-------------------------------------------------------------+--------+
| | DISTRIBUTED_STORAGE_CONFIG.local_us.secret_key is required | |
+ +-------------------------------------------------------------+--------+
| | DISTRIBUTED_STORAGE_CONFIG.local_us.hostname is required | |
+ +-------------------------------------------------------------+--------+
| | DISTRIBUTED_STORAGE_CONFIG.local_us.bucket_name is required | |

What am I doing wrong?

Thanks for helping.

Tom

 

1 Solution

Accepted Solutions
TomHutter
Mission Specialist
Mission Specialist
  • 364 Views

Never mind, today it worked.
I also see now DISTRIBUTED_STORAGE_CONFIG when running cat /conf/stack/config.yaml on one of the app pods:

oc exec -it central-quay-app-5957857b84-cjjcd -- cat /conf/stack/config.yaml

...
DISTRIBUTED_STORAGE_CONFIG:
local_us:
- RHOCSStorage
- access_key: OKp...3J5b99z
bucket_name: quay-datastore-c658dc60-...460a3bd05e
hostname: s3.openshift-storage.svc.cluster.local
is_secure: true
port: 443
secret_key: etCjm...C9Xw
storage_path: /datastorage/registry
DISTRIBUTED_STORAGE_DEFAULT_LOCATIONS:
- local_us
DISTRIBUTED_STORAGE_PREFERENCE:
- local_us
...

I assume a kind of race condition yesterday with creation of objectbucketclaim and pods

[student@workstation ~]$ oc get objectbucketclaims
NAME STORAGE-CLASS PHASE AGE
central-quay-datastore openshift-storage.noobaa.io Bound 16m

[student@workstation ~]$ oc get pods
NAME READY STATUS RESTARTS AGE
central-quay-app-5957857b84-cjjcd 1/1 Running 0 15m
central-quay-app-5957857b84-gnxlb 1/1 Running 1 (15m ago) 15m


View solution in original post

0 Kudos
2 Replies
TomHutter
Mission Specialist
Mission Specialist
  • 418 Views

Checking the config.yaml on the central-quay-config-editor Pod shows, there is no secret_key / hostname / bucket_name. At least not for the central-quay-config-editor Pod.

oc exec -it central-quay-config-editor-7ddb978d9c-kxtjn -- cat /conf/stack/config.yaml

...

DISTRIBUTED_STORAGE_CONFIG:
local_us:
- RHOCSStorage
- is_secure: true
port: 443
storage_path: /datastorage/registry
DISTRIBUTED_STORAGE_DEFAULT_LOCATIONS:
- local_us
DISTRIBUTED_STORAGE_PREFERENCE:
- local_us

...

0 Kudos
TomHutter
Mission Specialist
Mission Specialist
  • 365 Views

Never mind, today it worked.
I also see now DISTRIBUTED_STORAGE_CONFIG when running cat /conf/stack/config.yaml on one of the app pods:

oc exec -it central-quay-app-5957857b84-cjjcd -- cat /conf/stack/config.yaml

...
DISTRIBUTED_STORAGE_CONFIG:
local_us:
- RHOCSStorage
- access_key: OKp...3J5b99z
bucket_name: quay-datastore-c658dc60-...460a3bd05e
hostname: s3.openshift-storage.svc.cluster.local
is_secure: true
port: 443
secret_key: etCjm...C9Xw
storage_path: /datastorage/registry
DISTRIBUTED_STORAGE_DEFAULT_LOCATIONS:
- local_us
DISTRIBUTED_STORAGE_PREFERENCE:
- local_us
...

I assume a kind of race condition yesterday with creation of objectbucketclaim and pods

[student@workstation ~]$ oc get objectbucketclaims
NAME STORAGE-CLASS PHASE AGE
central-quay-datastore openshift-storage.noobaa.io Bound 16m

[student@workstation ~]$ oc get pods
NAME READY STATUS RESTARTS AGE
central-quay-app-5957857b84-cjjcd 1/1 Running 0 15m
central-quay-app-5957857b84-gnxlb 1/1 Running 1 (15m ago) 15m


0 Kudos
Join the discussion
You must log in to join this conversation.