Skip to content

OCPBUGS-20576: [release-4.11] CARRY: Add DOWNSTREAM_OWNERS#230

Merged
openshift-ci[bot] merged 1 commit intoopenshift:release-4.11from
openshift-cherrypick-robot:cherry-pick-223-to-release-4.11
Oct 13, 2023
Merged

OCPBUGS-20576: [release-4.11] CARRY: Add DOWNSTREAM_OWNERS#230
openshift-ci[bot] merged 1 commit intoopenshift:release-4.11from
openshift-cherrypick-robot:cherry-pick-223-to-release-4.11

Conversation

@openshift-cherrypick-robot
Copy link
Copy Markdown

@openshift-cherrypick-robot openshift-cherrypick-robot commented Oct 12, 2023

This is an automated cherry-pick of #223

/assign dulek

@dulek
CARRY: Add DOWNSTREAM_OWNERS
e4b792a 
This should allow us to remove the carry and avoid merge conflicts on
upstream OWNERS.
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Oct 12, 2023
Merged
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Oct 12, 2023

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

@dulek
Copy link
Copy Markdown

dulek commented Oct 13, 2023

/lgtm
/approve
/label backport-risk-assessed

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Oct 13, 2023

@dulek: Can not set label backport-risk-assessed: Must be member in one of these teams: [openshift-patch-managers]

Details

In response to this:

/lgtm
/approve
/label backport-risk-assessed

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 lgtm Indicates that a PR is ready to be merged. label Oct 13, 2023
mandre
mandre reviewed Oct 13, 2023
View reviewed changes
Copy link
Copy Markdown
Member

@mandre mandre 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 Oct 13, 2023
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Oct 13, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dulek, mandre, 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 Oct 13, 2023
@dulek
Copy link
Copy Markdown

dulek commented Oct 13, 2023

/retitle OCPBUGS-20576: [release-4.11] CARRY: Add DOWNSTREAM_OWNERS

@openshift-ci openshift-ci Bot changed the title [release-4.11] CARRY: Add DOWNSTREAM_OWNERS OCPBUGS-20576: [release-4.11] CARRY: Add DOWNSTREAM_OWNERS Oct 13, 2023
@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 Oct 13, 2023
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Oct 13, 2023

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

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

Details

In response to this:

This is an automated cherry-pick of #223

/assign dulek

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.

@rlobillo
Copy link
Copy Markdown

rlobillo commented Oct 13, 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 Oct 13, 2023
@dulek
Copy link
Copy Markdown

dulek commented Oct 13, 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. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Oct 13, 2023
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Oct 13, 2023

@dulek: This pull request references Jira Issue OCPBUGS-20576, 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.11.z) matches configured target version for branch (4.11.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-20573 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-20573 targets the "4.12.z" version, which is one of the valid target versions: 4.12.0, 4.12.z
  • bug has dependents

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

Details

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 merged commit 9eed4ed into openshift:release-4.11 Oct 13, 2023
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Oct 13, 2023

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

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

Details

In response to this:

This is an automated cherry-pick of #223

/assign dulek

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-merge-robot
Copy link
Copy Markdown

openshift-merge-robot commented Oct 16, 2023

Fix included in accepted release 4.11.0-0.nightly-2023-10-14-102406

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

Reviewers

@mandre mandre mandre left review comments

@pierreprinetti pierreprinetti Awaiting requested review from pierreprinetti

Assignees

@dulek dulek

@mandre mandre

@eurijon eurijon

@itzikb-redhat itzikb-redhat

@rlobillo rlobillo

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

8 participants

@openshift-cherrypick-robot @dulek @openshift-ci-robot @rlobillo @openshift-merge-robot @mandre @eurijon @itzikb-redhat