-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
-
False
-
Passed
-
0
-
0
-
0
-
None
Description of problem:
Registry pod is stuck on ContainerCreating when creating BSL with custom secret name and without snapshotLocations
Version-Release number of selected component (if applicable): 1.02
How reproducible: Always
Steps to reproduce: Create DPA with BSL and custom resource name without snapshotLocations list
Actual result:
[mperetz@mperetz oadp-e2e-qe]$ oc get dpa -n openshift-adp -o yaml
apiVersion: v1
items:
- apiVersion: oadp.openshift.io/v1alpha1
kind: DataProtectionApplication
metadata:
creationTimestamp: "2022-04-06T15:03:14Z"
generation: 1
name: ts-example-velero
namespace: openshift-adp
resourceVersion: "473812"
uid: 830dabff-3036-4b17-aeea-6049725028cc
spec:
backupLocations:
- velero:
credential:
key: cloud
name: bsl-cloud-credentials-gcp
default: true
objectStorage:
bucket: oadpbucket91559
prefix: velero-e2e-8c817310-7328-4641-b604-9b19b53dffaf
provider: gcp
configuration:
restic:
podConfig:
resourceAllocations: {}
velero:
defaultPlugins:
- openshift
- gcp
status:
conditions:
- lastTransitionTime: "2022-04-06T15:03:14Z"
message: Reconcile complete
reason: Complete
status: "True"
type: Reconciled
kind: List
metadata:
resourceVersion: ""
selfLink: ""
[mperetz@mperetz oadp-e2e-qe]$ oc get pods -n openshift-adp
NAME READY STATUS RESTARTS AGE
oadp-ts-example-velero-1-gcp-registry-7ccfbb5c54-hdgh7 0/1 ContainerCreating 0 5m7s
openshift-adp-controller-manager-989594688-j9xzw 1/1 Running 0 6h49m
velero-7c7fc5bf4c-qqzwq 1/1 Running 0 5m7s
[mperetz@mperetz oadp-e2e-qe]$
Expected result: Registry pod should not get stuck on ContainerCreating when using custom secret on BSL