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.

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

Bug 2050189: Rebase v1.3.6 #16

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #15

/assign bertinatto

@bertinatto
Copy link
Member

/retitle [release-4.10] Bug: 2050180: Rebase v1.3.6

@openshift-ci openshift-ci bot changed the title [release-4.10] Rebase v1.3.6 [release-4.10] Bug: 2050180: Rebase v1.3.6 Feb 3, 2022
@openshift-ci
Copy link

openshift-ci bot commented Feb 3, 2022

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

[release-4.10] Bug: 2050180: Rebase v1.3.6

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.

@bertinatto
Copy link
Member

bertinatto commented Feb 3, 2022

/retitle Bug 2050180: Rebase v1.3.6

@openshift-ci
Copy link

openshift-ci bot commented Feb 3, 2022

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

Bug: 2050180: Rebase v1.3.6

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 changed the title [release-4.10] Bug: 2050180: Rebase v1.3.6 Bug: 2050180: Rebase v1.3.6 Feb 3, 2022
@bertinatto
Copy link
Member

/retitle Bug 2050180: Rebase v1.3.6

@openshift-ci openshift-ci bot changed the title Bug: 2050180: Rebase v1.3.6 Bug 2050180: Rebase v1.3.6 Feb 3, 2022
@openshift-ci
Copy link

openshift-ci bot commented Feb 3, 2022

@openshift-cherrypick-robot: 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.

@openshift-ci openshift-ci bot added the bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. label Feb 3, 2022
@openshift-ci
Copy link

openshift-ci bot commented Feb 3, 2022

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

  • expected the bug to target the "4.10.0" release, but it targets "4.10.z" instead
  • expected Bugzilla bug 2050180 to depend on a bug targeting a release in 4.11.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.

In response to this:

Bug 2050180: Rebase v1.3.6

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 added the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Feb 3, 2022
@bertinatto
Copy link
Member

/bugzilla refresh

@openshift-ci
Copy link

openshift-ci bot commented Feb 3, 2022

@bertinatto: This pull request references Bugzilla bug 2050180, which is invalid:

  • expected Bugzilla bug 2050180 to depend on a bug targeting a release in 4.11.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.

In response to this:

/bugzilla 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.

@bertinatto
Copy link
Member

/retitle Bug 2050189: Rebase v1.3.6

@openshift-ci openshift-ci bot changed the title Bug 2050180: Rebase v1.3.6 Bug 2050189: Rebase v1.3.6 Feb 3, 2022
@openshift-ci
Copy link

openshift-ci bot commented Feb 3, 2022

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

  • expected the bug to target the "4.10.0" release, but it targets "4.11.0" instead

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.

In response to this:

Bug 2050189: Rebase v1.3.6

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.

@bertinatto
Copy link
Member

/bugzilla refresh

@openshift-ci
Copy link

openshift-ci bot commented Feb 3, 2022

@bertinatto: This pull request references Bugzilla bug 2050189, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is ON_QA instead

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.

In response to this:

/bugzilla 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.

@bertinatto
Copy link
Member

/bugzilla refresh

@openshift-ci openshift-ci bot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Feb 3, 2022
@openshift-ci
Copy link

openshift-ci bot commented Feb 3, 2022

@bertinatto: This pull request references Bugzilla bug 2050189, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.10.0) matches configured target release for branch (4.10.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 2050180 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Bugzilla bug 2050180 targets the "4.11.0" release, which is one of the valid target releases: 4.11.0
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Bugzilla (wduan@redhat.com), skipping review request.

In response to this:

/bugzilla 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 removed the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Feb 3, 2022
@dobsonj
Copy link
Member

dobsonj commented Feb 4, 2022

/lgtm
/approve
/label backport-risk-assessed

/cc @duanwei33
for QE approval

will need staff eng approval if QE is okay with this.

@openshift-ci openshift-ci bot requested a review from duanwei33 February 4, 2022 17:42
@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 Feb 4, 2022
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 4, 2022
@openshift-ci
Copy link

openshift-ci bot commented Feb 4, 2022

[APPROVALNOTIFIER] This PR is APPROVED

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

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 Feb 4, 2022
@duanwei33
Copy link

/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 Feb 5, 2022
@openshift-merge-robot openshift-merge-robot merged commit 39d2449 into openshift:release-4.10 Feb 5, 2022
@openshift-ci
Copy link

openshift-ci bot commented Feb 5, 2022

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

Bugzilla bug 2050189 has been moved to the MODIFIED state.

In response to this:

Bug 2050189: Rebase v1.3.6

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-medium Referenced Bugzilla bug's severity is medium 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

10 participants