Skip to content

Bug 2113927: [release-4.11] Exits with a non-zero code in case Etcd backup fails#903

Merged
openshift-merge-robot merged 3 commits intoopenshift:release-4.11from
openshift-cherrypick-robot:cherry-pick-871-to-release-4.11
Aug 17, 2022
Merged

Bug 2113927: [release-4.11] Exits with a non-zero code in case Etcd backup fails#903
openshift-merge-robot merged 3 commits intoopenshift:release-4.11from
openshift-cherrypick-robot:cherry-pick-871-to-release-4.11

Conversation

@openshift-cherrypick-robot
Copy link
Copy Markdown

This is an automated cherry-pick of #871

/assign tjungblu

@tjungblu
Copy link
Copy Markdown
Contributor

tjungblu commented Aug 2, 2022

/cherry-pick release-4.10

@openshift-cherrypick-robot
Copy link
Copy Markdown
Author

@tjungblu: once the present PR merges, I will cherry-pick it on top of release-4.10 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick release-4.10

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.

@openshift-ci openshift-ci Bot requested review from Elbehery and tjungblu August 2, 2022 10:41
@tjungblu tjungblu changed the title [release-4.11] Exits with a non-zero code in case Etcd backup fails Bug 2113927: [release-4.11] Exits with a non-zero code in case Etcd backup fails Aug 2, 2022
@openshift-ci openshift-ci Bot added bugzilla/severity-low Referenced Bugzilla bug's severity is low for the branch this PR is targeting. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Aug 2, 2022
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Aug 2, 2022

@openshift-cherrypick-robot: This pull request references Bugzilla bug 2113927, which is invalid:

  • expected the bug to target the "4.11.0" release, but it targets "---" instead
  • expected Bugzilla bug 2113927 to depend on a bug targeting a release in 4.12.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

Bug 2113927: [release-4.11] Exits with a non-zero code in case Etcd backup fails

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.

@tjungblu tjungblu added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Aug 2, 2022
@Elbehery
Copy link
Copy Markdown
Contributor

Elbehery commented Aug 2, 2022

/retest

Copy link
Copy Markdown
Contributor

@Elbehery Elbehery left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 2, 2022
@fsoppelsa
Copy link
Copy Markdown
Contributor

/retest

@tjungblu
Copy link
Copy Markdown
Contributor

/test e2e-agnostic-upgrade

@dusk125
Copy link
Copy Markdown
Contributor

dusk125 commented Aug 16, 2022

/approve
/label backport-risk-assessed

@openshift-ci openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Aug 16, 2022
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Aug 16, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dusk125, Elbehery, openshift-cherrypick-robot

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 16, 2022
@tjungblu tjungblu added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Aug 17, 2022
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Aug 17, 2022

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

@openshift-merge-robot openshift-merge-robot merged commit 7068edc into openshift:release-4.11 Aug 17, 2022
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Aug 17, 2022

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged:

Bugzilla bug 2113927 has been moved to the MODIFIED state.

Details

In response to this:

Bug 2113927: [release-4.11] Exits with a non-zero code in case Etcd backup fails

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.

@openshift-cherrypick-robot
Copy link
Copy Markdown
Author

@tjungblu: new pull request created: #907

Details

In response to this:

/cherry-pick release-4.10

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. bugzilla/severity-low Referenced Bugzilla bug's severity is low for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. lgtm Indicates that a PR is ready to be merged. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants