OCPBUGS-200: Exits with a non-zero code in case Etcd backup fails #907

openshift-cherrypick-robot · 2022-08-17T12:13:07Z

This is an automated cherry-pick of #903

/assign tjungblu

…eckable for monitoring purposes

…ase of an error

openshift-ci · 2022-08-17T12:13:19Z

@openshift-cherrypick-robot: An error was encountered cloning bug for cherrypick for bug 2113927 on the Bugzilla server at https://bugzilla.redhat.com. No known errors were detected, please see the full error message for details.

Full error message.


response code 401 not 200

Please contact an administrator to resolve this issue, then request a bug refresh with /bugzilla refresh.

Details

In 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.

openshift-ci-robot · 2022-08-17T12:20:02Z

@openshift-cherrypick-robot: This pull request references [Jira Issue OCPBUGS-200](https://issues.redhat.com//browse/OCPBUGS-200), which is invalid:

expected [Jira Issue OCPBUGS-200](https://issues.redhat.com//browse/OCPBUGS-200) to depend on a bug targeting a version in 4.11.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but no dependents were found

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

Details

In 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.

tjungblu · 2022-08-17T12:20:04Z

/jira update

openshift-ci · 2022-08-17T12:20:15Z

@openshift-cherrypick-robot: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In 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.

tjungblu · 2022-08-17T12:21:48Z

/jira refresh

openshift-ci-robot · 2022-08-17T12:21:51Z

@tjungblu: This pull request references [Jira Issue OCPBUGS-200](https://issues.redhat.com//browse/OCPBUGS-200), which is invalid:

expected dependent Jira Issue OCPBUGSM-47375 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is Code Review instead
expected dependent Jira Issue OCPBUGSM-47375 to target a version in 4.11.0, but no target version was set

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

Details

In 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.

openshift-ci · 2022-08-17T15:03:51Z

@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.

tjungblu · 2022-08-17T15:50:00Z

/jira refresh

openshift-ci-robot · 2022-08-17T15:50:40Z

@tjungblu: This pull request references [Jira Issue OCPBUGS-200](https://issues.redhat.com//browse/OCPBUGS-200), which is invalid:

expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is In Progress instead
expected dependent Jira Issue OCPBUGSM-47375 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is Code Review instead
expected dependent Jira Issue OCPBUGSM-47375 to target a version in 4.11.0, but no target version was set

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

Details

In 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.

Elbehery

/lgtm

tjungblu · 2022-08-17T16:05:04Z

/jira refresh

openshift-ci-robot · 2022-08-17T16:05:06Z

@tjungblu: This pull request references [Jira Issue OCPBUGS-200](https://issues.redhat.com//browse/OCPBUGS-200), which is invalid:

expected dependent Jira Issue OCPBUGSM-47375 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is Code Review instead
expected dependent Jira Issue OCPBUGSM-47375 to target a version in 4.11.0, but no target version was set

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

Details

In 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.

tjungblu · 2022-08-17T16:06:40Z

/jira refresh

openshift-ci-robot · 2022-08-17T16:06:43Z

@tjungblu: This pull request references [Jira Issue OCPBUGS-200](https://issues.redhat.com//browse/OCPBUGS-200), which is invalid:

expected dependent Jira Issue OCPBUGSM-47375 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is Code Review instead
expected dependent Jira Issue OCPBUGSM-47375 to target a version in 4.11.0, but it targets "4.11.z" instead

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

Details

In 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.

tjungblu · 2022-08-17T16:20:06Z

the depedency validation on 4.11.0 vs. 4.11.z should be fixed with openshift/release#31412

dusk125 · 2022-08-17T16:39:08Z

/approve
/label backport-risk-assessed

tjungblu · 2022-08-17T16:58:39Z

/jira refresh

openshift-ci-robot · 2022-08-17T16:58:42Z

@tjungblu: This pull request references [Jira Issue OCPBUGS-200](https://issues.redhat.com//browse/OCPBUGS-200), which is invalid:

expected dependent Jira Issue OCPBUGSM-47375 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is Code Review instead
expected dependent Jira Issue OCPBUGSM-47375 to target a version in 4.11.0, but it targets "4.11.z" instead

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

Details

In 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.

EmilyM1 · 2022-08-17T17:45:07Z

/lgtm

openshift-ci · 2022-08-17T17:45:34Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dusk125, Elbehery, EmilyM1, 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:

~~OWNERS~~ [dusk125]

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

tjungblu · 2022-08-18T15:01:22Z

/jira refresh

openshift-ci-robot · 2022-08-18T15:01:25Z

@tjungblu: This pull request references [Jira Issue OCPBUGS-200](https://issues.redhat.com//browse/OCPBUGS-200), which is invalid:

expected dependent Jira Issue OCPBUGSM-47375 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is Code Review instead
expected dependent Jira Issue OCPBUGSM-47375 to target a version in 4.11.0, but it targets "4.11.z" instead

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

Details

In 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.

tjungblu · 2022-08-18T15:02:22Z

I'm going to override the the bug here, clearly that jira bot is not knowing what it is doing.

openshift-ci-robot · 2022-08-18T15:05:51Z

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

openshift/cluster-etcd-operator#907

[Jira Issue OCPBUGS-200](https://issues.redhat.com//browse/OCPBUGS-200) has been moved to the MODIFIED state.

Details

In 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.

tjungblu · 2022-08-18T15:08:29Z

@fsoppelsa fyi, will go into the next 4.10.z

fsoppelsa added 3 commits August 17, 2022 12:13

Exits with a non-zero error in case Etcd backup fails, so it'll be ch…

966e553

…eckable for monitoring purposes

check where this is called and exit with a non-zero status there in c…

aa3c933

…ase of an error

fixes a mistake where I deleted a return 1

61a1532

openshift-cherrypick-robot mentioned this pull request Aug 17, 2022

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

Merged

openshift-ci bot assigned tjungblu Aug 17, 2022

openshift-ci bot requested review from Elbehery and dusk125 August 17, 2022 12:14

tjungblu changed the title ~~[release-4.10] Bug 2113927: Exits with a non-zero code in case Etcd backup fails~~ OCPBUGS-200: Exits with a non-zero code in case Etcd backup fails Aug 17, 2022

openshift-ci-robot added jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 17, 2022

Elbehery approved these changes Aug 17, 2022

View reviewed changes

openshift-ci bot assigned Elbehery Aug 17, 2022

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 17, 2022

openshift-ci bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Aug 17, 2022

openshift-ci bot assigned EmilyM1 Aug 17, 2022

openshift-merge-robot merged commit f39e514 into openshift:release-4.10 Aug 18, 2022

OCPBUGS-200: Exits with a non-zero code in case Etcd backup fails #907

OCPBUGS-200: Exits with a non-zero code in case Etcd backup fails #907

Uh oh!

Conversation

openshift-cherrypick-robot commented Aug 17, 2022

Uh oh!

openshift-ci bot commented Aug 17, 2022

Uh oh!

openshift-ci-robot commented Aug 17, 2022 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

tjungblu commented Aug 17, 2022

Uh oh!

openshift-ci bot commented Aug 17, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

tjungblu commented Aug 17, 2022

Uh oh!

openshift-ci-robot commented Aug 17, 2022 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci bot commented Aug 17, 2022

Uh oh!

tjungblu commented Aug 17, 2022

Uh oh!

openshift-ci-robot commented Aug 17, 2022 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Elbehery left a comment

Choose a reason for hiding this comment

Uh oh!

tjungblu commented Aug 17, 2022

Uh oh!

openshift-ci-robot commented Aug 17, 2022 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

tjungblu commented Aug 17, 2022

Uh oh!

openshift-ci-robot commented Aug 17, 2022 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

tjungblu commented Aug 17, 2022

Uh oh!

dusk125 commented Aug 17, 2022

Uh oh!

tjungblu commented Aug 17, 2022

Uh oh!

openshift-ci-robot commented Aug 17, 2022 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

EmilyM1 commented Aug 17, 2022

Uh oh!

openshift-ci bot commented Aug 17, 2022

Uh oh!

tjungblu commented Aug 18, 2022

Uh oh!

openshift-ci-robot commented Aug 18, 2022 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

tjungblu commented Aug 18, 2022

Uh oh!

openshift-ci-robot commented Aug 18, 2022 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

tjungblu commented Aug 18, 2022

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

8 participants

openshift-ci-robot commented Aug 17, 2022 •

edited by openshift-ci bot

Loading

openshift-ci bot commented Aug 17, 2022 •

edited

Loading

openshift-ci-robot commented Aug 17, 2022 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Aug 17, 2022 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Aug 17, 2022 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Aug 17, 2022 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Aug 17, 2022 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Aug 18, 2022 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Aug 18, 2022 •

edited by openshift-ci bot

Loading