Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[4.9] Bug OCPBUGS-1246: Improve resiliency of eTag handling #317

Merged
merged 1 commit into from Dec 14, 2022
Merged

[4.9] Bug OCPBUGS-1246: Improve resiliency of eTag handling #317

merged 1 commit into from Dec 14, 2022

Conversation

rhjanders
Copy link

This commit brings the upstream OpenStack/Sushy fixes improving eTag handling into OpenShift 4.9

https://review.opendev.org/c/openstack/sushy/+/862849

@rhjanders
[4.9] Improve resiliency of eTag handling
25e457c 
This commit brings the upstream OpenStack/Sushy fixes improving eTag
handling into OpenShift 4.9

https://review.opendev.org/c/openstack/sushy/+/862849
@openshift-ci
Copy link

openshift-ci bot commented Nov 9, 2022

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

In response to this:

[4.9] Improve resiliency of eTag handling

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.

@elfosardo
Copy link

/approve

@openshift-ci
Copy link

openshift-ci bot commented Nov 9, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: elfosardo, rhjanders

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

The pull request process is described here

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 Nov 9, 2022
@rhjanders
Copy link
Author

/test prevalidation-images

@rhjanders
Copy link
Author

/test prevalidation-e2e-metal-ipi-virtualmedia-prevalidation

@rhjanders
Copy link
Author

/test prevalidation-e2e-metal-ipi-prevalidation

@rhjanders
Copy link
Author

/retest

@rhjanders rhjanders changed the title [4.9] Improve resiliency of eTag handling [4.9] Bug OCPBUGS-1246 : Improve resiliency of eTag handling Nov 10, 2022
@openshift-ci
Copy link

openshift-ci bot commented Nov 10, 2022

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

In response to this:

[4.9] Bug OCPBUGS-1246 : Improve resiliency of eTag handling

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.

@rhjanders
Copy link
Author

/jira refresh

@rhjanders rhjanders changed the title [4.9] Bug OCPBUGS-1246 : Improve resiliency of eTag handling [4.9] Bug OCPBUGS-1246: Improve resiliency of eTag handling Nov 10, 2022
@openshift-ci
Copy link

openshift-ci bot commented Nov 10, 2022

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

In response to this:

[4.9] Bug OCPBUGS-1246: Improve resiliency of eTag handling

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 openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important 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 Nov 10, 2022
@openshift-ci-robot
Copy link

@rhjanders: This pull request references Jira Issue OCPBUGS-1246, which is invalid:

  • expected dependent Jira Issue OCPBUGS-3477 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is New 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.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This commit brings the upstream OpenStack/Sushy fixes improving eTag handling into OpenShift 4.9

https://review.opendev.org/c/openstack/sushy/+/862849

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.

@rhjanders
Copy link
Author

/jira refresh

@openshift-ci-robot
Copy link

@rhjanders: This pull request references Jira Issue OCPBUGS-1246, which is invalid:

  • expected dependent Jira Issue OCPBUGS-3477 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is New 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.

In response to this:

/jira refresh

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.

@rhjanders
Copy link
Author

/jira refresh

@openshift-ci-robot
Copy link

@rhjanders: This pull request references Jira Issue OCPBUGS-1246, which is invalid:

  • expected dependent Jira Issue OCPBUGS-3477 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is POST 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.

In response to this:

/jira refresh

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.

@iurygregory iurygregory added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Nov 18, 2022
@elfosardo
Copy link

/retest

2 similar comments
@elfosardo
Copy link

/retest

@elfosardo
Copy link

/retest

@elfosardo
Copy link

/retes

@elfosardo
Copy link

/retest

1 similar comment
@elfosardo
Copy link

/retest

@elfosardo
Copy link

/retest

@openshift-ci
Copy link

openshift-ci bot commented Nov 22, 2022

@rhjanders: all tests passed!

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.

@iurygregory iurygregory added the lgtm Indicates that a PR is ready to be merged. label Nov 24, 2022
@rhjanders
Copy link
Author

/jira refresh

@openshift-ci-robot
Copy link

@rhjanders: This pull request references Jira Issue OCPBUGS-1246, which is invalid:

  • expected dependent Jira Issue OCPBUGS-3477 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is POST 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.

In response to this:

/jira refresh

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.

@rhjanders
Copy link
Author

/jira refresh

@openshift-ci-robot
Copy link

@rhjanders: This pull request references Jira Issue OCPBUGS-1246, which is invalid:

  • expected dependent Jira Issue OCPBUGS-3477 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is MODIFIED 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.

In response to this:

/jira refresh

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.

@rhjanders
Copy link
Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid 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. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Dec 14, 2022
@openshift-ci-robot
Copy link

@rhjanders: This pull request references Jira Issue OCPBUGS-1246, which is valid.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.9.z) matches configured target version for branch (4.9.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-3477 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
  • dependent Jira Issue OCPBUGS-3477 targets the "4.10.z" version, which is one of the valid target versions: 4.10.0, 4.10.z
  • bug has dependents

In response to this:

/jira refresh

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.

@jadhaj
Copy link

jadhaj commented Dec 14, 2022

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Dec 14, 2022
@openshift-merge-robot openshift-merge-robot merged commit 8e978cd into openshift:release-4.9 Dec 14, 2022
@openshift-ci-robot
Copy link

@rhjanders: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-1246 has been moved to the MODIFIED state.

In response to this:

This commit brings the upstream OpenStack/Sushy fixes improving eTag handling into OpenShift 4.9

https://review.opendev.org/c/openstack/sushy/+/862849

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
Reviewers

@dtantsur dtantsur Awaiting requested review from dtantsur

@elfosardo elfosardo Awaiting requested review from elfosardo

Assignees
No one assigned
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/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. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
6 participants
@rhjanders @elfosardo @openshift-ci-robot @jadhaj @iurygregory @openshift-merge-robot