-
Notifications
You must be signed in to change notification settings - Fork 86
Replace carriage return when getting provider secrets for registry #650
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Note that e2e doesn't properly test carriage return secret selected in registry. Fix coming in a separate PR which should be merged before this to test e2e. |
|
If #652 e2e-test says has this log with bsl-cloud-credentials-aws-with-carriage-return we are good to go. 2022-04-28T19:55:04.434-0400 INFO controller.dataprotectionapplication got provider secret name: bsl-cloud-credentials-aws-with-carriage-return {"reconciler group": "oadp.openshift.io", "reconciler kind": "DataProtectionApplication", "name": "ts-example-velero", "namespace": "openshift-adp"}#650 alone is not able to set and see the modified credentials working mid-test for registry deployment e2e. Additionally you should see "carriage return replaced" print out in oadp-controller-manager log |
|
Manual testing show registry pod no longer errors with |
Co-authored-by: GitHub Co-pilot <idkwhatemailgithubcopilotuses@github.com>
e1eb0df to
dce9b99
Compare
|
/retest |
3 similar comments
|
/retest |
|
/retest |
|
/retest |
|
/retest |
This is useful for debugging pods not starting up or stuck. Example event that would come up before openshift#650 is merged ``` Event: Error: couldn't find key access_key in Secret openshift-adp/oadp-ts-example-velero-1-aws-registry-secret, Src: kubelet, Reason: Failed ```
|
/retest |
1 similar comment
|
/retest |
|
@kaovilai: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
closing in favor of #652 |
This is useful for debugging pods not starting up or stuck. Example event that would come up before openshift#650 is merged ``` Event: Error: couldn't find key access_key in Secret openshift-adp/oadp-ts-example-velero-1-aws-registry-secret, Src: kubelet, Reason: Failed ```
…wait for CSI snapshot to be ready, IsDCReady wait for builds, azure-rg (#654) * Print namespace events when installing apps fail This is useful for debugging pods not starting up or stuck. Example event that would come up before #650 is merged ``` Event: Error: couldn't find key access_key in Secret openshift-adp/oadp-ts-example-velero-1-aws-registry-secret, Src: kubelet, Reason: Failed ``` * use metav1 Time * format * Get events after time * add sort and count to event * Update lastInstallTime and lastInstallApplicationNamespace for app restore * Add restic restore workaround to e2e. Add opts for CreateRestoreFromBackup * Implementing DC workaround in e2e https://github.com/openshift/oadp-operator/blob/master/docs/TROUBLESHOOTING.md#deployconfig * Handle IsNotRegisteredError * different restore name for workaround * try add templatev1 to scheme * updateLastInstallingNamespace func * E2E Wait for snapshot to be ready for CSI B/R case Fix ``` Event: failed to provision volume with StorageClass "gp2-csi": error getting handle for DataSource Type VolumeSnapshot by Name velero-mysql-l5sz5: snapshot velero-mysql-l5sz5 is not Ready, Type: Warning, Count: 10, Src: {PersistentVolumeClaim mysql-persistent mysql 72d98c8-10ff-4a32-a319-88bed69e1227 v1 34225 }, Reason: ProvisioningFailed ``` seen at https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_oadp-operator/654/pull-ci-openshift-oadp-operator-master-4.9-operator-e2e-aws/1520234660829859840#1:build-log.txt%3A375 * addToScheme volumesnapshotv1 * check volumesnapshots by label * Describe backup and restore in backup restore suite test * format * fix make test, install.AllCRDs param removal * log so we know we are waiting on volumesnapshot * Wait for builds before considering app ready * move B/R describe to ginkgowriter * add builds ready check to after restic DC restore workaround first step * IsVolumeSnapshotsReady ->AreVolumeSnapshotsReady * use correct restore name to check for done * Use GinkgoWriter for describe * fix getVeleroPods labels * B/R logs request via downloadrequest * Check cluster version skip before building dpa * Azure resource group (#45) * fix awk for azure resource group * newline proof awk for resourcegroup * remove unused commented codes * break loop after found DC availability condition * rebase reverted go.mod velero update * make test go fmt * use log.Printf
OADP-463
Close #621