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

OCPBUGS-5029: [release-4.13] OpenStack: Restore in-tree cinder provisioner tests #27827

Merged
merged 1 commit into from Jun 7, 2023
Merged

OCPBUGS-5029: [release-4.13] OpenStack: Restore in-tree cinder provisioner tests #27827

merged 1 commit into from Jun 7, 2023

Conversation

openshift-cherrypick-robot
Copy link

This is an automated cherry-pick of #27789

/assign mandre

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Mar 28, 2023
Merged
@mandre
Copy link
Member

mandre commented Mar 29, 2023

/retest

@mandre
Copy link
Member

mandre commented Mar 30, 2023

The e2e-openstack-ovn failure is caused by https://issues.redhat.com/browse/OCPBUGS-11112.
/retest-required

@mandre
Copy link
Member

mandre commented Mar 30, 2023

/rename OCPBUGS-5029: [release-4.13] OpenStack: Restore in-tree cinder provisioner tests

@mandre
Copy link
Member

mandre commented Mar 30, 2023

/jira refresh

@openshift-ci-robot
Copy link

@mandre: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

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.

@mandre
Copy link
Member

mandre commented Mar 30, 2023

/retitle OCPBUGS-5029: [release-4.13] OpenStack: Restore in-tree cinder provisioner tests

@openshift-ci openshift-ci bot changed the title [release-4.13] OpenStack: Restore in-tree cinder provisioner tests OCPBUGS-5029: [release-4.13] OpenStack: Restore in-tree cinder provisioner tests Mar 30, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 30, 2023

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

In response to this:

OCPBUGS-5029: [release-4.13] OpenStack: Restore in-tree cinder provisioner tests

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/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Mar 30, 2023
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-5029, which is invalid:

  • expected Jira Issue OCPBUGS-5029 to depend on a bug targeting a version in 4.14.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, 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.

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

In response to this:

This is an automated cherry-pick of #27789

/assign mandre

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.

@mandre
Copy link
Member

mandre commented Mar 30, 2023

/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 Mar 30, 2023
@openshift-ci-robot
Copy link

@mandre: This pull request references Jira Issue OCPBUGS-5029, which is valid. The bug has been moved to the POST state.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.13.0) matches configured target version for branch (4.13.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-11122 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-11122 targets the "4.14.0" version, which is one of the valid target versions: 4.14.0
  • bug has dependents

Requesting review from QA contact:
/cc @eurijon

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.

@openshift-ci openshift-ci bot requested a review from eurijon March 30, 2023 10:48
@mandre
Copy link
Member

mandre commented Apr 6, 2023

/retest

1 similar comment
@mandre
Copy link
Member

mandre commented May 9, 2023

/retest

@mandre
Copy link
Member

mandre commented May 11, 2023

Hmm, my last comment didn't trigger a re-run of the failed jobs.

/retest

@mandre
Copy link
Member

mandre commented May 11, 2023

CI looks good.
/assign @soltysh

soltysh
soltysh approved these changes Jun 1, 2023
View reviewed changes
Copy link
Member

@soltysh soltysh left a comment

Choose a reason for hiding this comment

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

/lgtm
/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 Jun 1, 2023
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 1, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 1, 2023

[APPROVALNOTIFIER] This PR is APPROVED

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

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 Jun 1, 2023
@gangwgr
Copy link
Contributor

gangwgr commented Jun 1, 2023

/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 Jun 1, 2023
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD f210c2d and 2 for PR HEAD 0357ebd in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 1, 2023 •
edited

@openshift-cherrypick-robot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-ovn-single-node-upgrade 0357ebd link false /test e2e-aws-ovn-single-node-upgrade

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.

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD f210c2d and 2 for PR HEAD 0357ebd in total

@openshift-merge-robot openshift-merge-robot merged commit dfd4e79 into openshift:release-4.13 Jun 7, 2023
26 of 27 checks passed
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-5029: All pull requests linked via external trackers have merged:

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

In response to this:

This is an automated cherry-pick of #27789

/assign mandre

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

@soltysh soltysh soltysh approved these changes

@ashishkamra ashishkamra Awaiting requested review from ashishkamra

@csrwng csrwng Awaiting requested review from csrwng

@eurijon eurijon Awaiting requested review from eurijon

Assignees

@dgoodwin dgoodwin

@mandre mandre

@stbenjam stbenjam

@soltysh soltysh

@kasturinarra kasturinarra

@jadhaj jadhaj

@pamoedom pamoedom

@jitendar-singh jitendar-singh

@prietyc123 prietyc123

@gangwgr gangwgr

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/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. 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