Exits with a non-zero code in case Etcd backup fails#871
Exits with a non-zero code in case Etcd backup fails#871openshift-merge-robot merged 3 commits intoopenshift:masterfrom
Conversation
…eckable for monitoring purposes
|
@fsoppelsa thanks, I think you also need to run |
|
/test verify |
|
There appears a difference in bin data. @tjungblu has a great suggestion and |
|
I don't know if this is supposed to work as if I run |
hello ✋🏽 , can you run If it does not complain, then we are fine, Please keep me updated |
|
That looks fine, where is the mistake that could break the code you were referring to ? |
This file pkg/operator/etcd_assets/bindata.go but I think it's a big comment: |
I reviewed the changes character by character, and I could not find a mistake .. So what you have done is right, you edit |
|
/retest-required |
1 similar comment
|
/retest-required |
|
/lgtm |
|
/assign @dusk125 |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dusk125, Elbehery, fsoppelsa The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest-required |
|
/retest-required |
|
/retest |
|
/retest-required |
|
@Elbehery so apparently tests are failing on ci/prow/e2e-aws-single-node , why? 🤔 Is there anything wrong in this (tiny) commit that breaks aws-sno? |
|
/retest-required SNO is flaky for us for a while, but it's sometimes OVN, today it's network edge. |
|
if that's not coming through today, I'd ask @dusk125 to override the test today. It's clearly not related to your script. |
|
Moving this forward since the failure is unrelated to etcd |
|
@dusk125: Overrode contexts on behalf of dusk125: ci/prow/e2e-aws-single-node DetailsIn response to this:
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. |
|
@fsoppelsa: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
/cherry-pick release-4.11 |
|
@tjungblu: new pull request created: #903 DetailsIn response to this:
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. |
So cluster-backup.sh exits with non-zero and this return code is usable for monitoring purposes.