Skip to content

[release-4.12] OCPBUGS-54147: Add/remove team members to the OWNERS file for Builds #29622

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
Merged
merged 1 commit into from
Apr 25, 2025
Merged

[release-4.12] OCPBUGS-54147: Add/remove team members to the OWNERS file for Builds #29622

merged 1 commit into from
Apr 25, 2025

Conversation

openshift-cherrypick-robot
Copy link

This is an automated cherry-pick of #29608

/assign kunalmemane

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Mar 24, 2025
Merged
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-53285 has been cloned as Jira Issue OCPBUGS-54147. Will retitle bug to link to clone.
/retitle [release-4.12] OCPBUGS-54147: Add/remove team members to the OWNERS file for Builds

In response to this:

This is an automated cherry-pick of #29608

/assign kunalmemane

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot changed the title [release-4.12] OCPBUGS-53285: Add/remove team members to the OWNERS file for Builds [release-4.12] OCPBUGS-54147: Add/remove team members to the OWNERS file for Builds Mar 24, 2025
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. 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 24, 2025
@openshift-ci-robot
Copy link

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

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

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 #29608

/assign kunalmemane

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 openshift-eng/jira-lifecycle-plugin repository.

@kunalmemane
Copy link
Contributor

/retest
/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 Mar 24, 2025
@openshift-ci-robot
Copy link

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

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.12.z) matches configured target version for branch (4.12.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-53285 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-53285 targets the "4.13.z" version, which is one of the valid target versions: 4.13.0, 4.13.z
  • bug has dependents

In response to this:

/retest
/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 openshift-eng/jira-lifecycle-plugin repository.

@gabemontero
Copy link
Contributor

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 24, 2025
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Mar 24, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gabemontero, 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 Mar 24, 2025
@kunalmemane
Copy link
Contributor

/test e2e-gcp-ovn-builds

@kunalmemane
Copy link
Contributor

/retest

@kunalmemane
Copy link
Contributor

/test e2e-gcp-ovn-builds

1 similar comment
@kunalmemane
Copy link
Contributor

/test e2e-gcp-ovn-builds

@kunalmemane
Copy link
Contributor

/retest

@prabhapa
Copy link
Contributor

/test e2e-gcp-ovn-builds

@kunalmemane
Copy link
Contributor

/retest

@kunalmemane
Copy link
Contributor

/test e2e-gcp-ovn-builds

1 similar comment
@kunalmemane
Copy link
Contributor

/test e2e-gcp-ovn-builds

@sosiouxme
Copy link
Member

/override ci/prow/e2e-gcp-ovn-builds
per slack request
approval/lgtm already applied
/retest

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Apr 24, 2025

@sosiouxme: Overrode contexts on behalf of sosiouxme: ci/prow/e2e-gcp-ovn-builds

In response to this:

/override ci/prow/e2e-gcp-ovn-builds
per slack request
approval/lgtm already applied
/retest

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-sigs/prow repository.

@prabhapa
Copy link
Contributor

/label backport-risk-assessed
/label cherry-pick-approved

@openshift-ci openshift-ci bot added 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. labels Apr 25, 2025
@tonyxrmdavidson
Copy link

/test e2e-gcp-ovn-builds

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 893161e and 2 for PR HEAD 23d2495 in total

@sosiouxme
Copy link
Member

/override ci/prow/e2e-gcp-ovn-builds

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Apr 25, 2025

@sosiouxme: Overrode contexts on behalf of sosiouxme: ci/prow/e2e-gcp-ovn-builds

In response to this:

/override ci/prow/e2e-gcp-ovn-builds

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-sigs/prow repository.

@openshift-merge-bot openshift-merge-bot bot merged commit 3b2567f into openshift:release-4.12 Apr 25, 2025
19 of 23 checks passed
@openshift-ci-robot
Copy link

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

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

In response to this:

This is an automated cherry-pick of #29608

/assign kunalmemane

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Apr 25, 2025

@openshift-cherrypick-robot: The following tests 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-agnostic-ovn-cmd 23d2495 link false /test e2e-agnostic-ovn-cmd
ci/prow/e2e-gcp-csi 23d2495 link false /test e2e-gcp-csi
ci/prow/e2e-gcp-ovn-rt-upgrade 23d2495 link false /test e2e-gcp-ovn-rt-upgrade
ci/prow/e2e-aws-ovn-upgrade 23d2495 link false /test e2e-aws-ovn-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-sigs/prow repository. I understand the commands that are listed here.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-tests
This PR has been included in build openshift-enterprise-tests-container-v4.12.0-202504251430.p0.g3b2567f.assembly.stream.el8.
All builds following this will include this PR.

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.12.0-0.nightly-2025-04-25-161402

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

@coreydaley coreydaley Awaiting requested review from coreydaley

@gabemontero gabemontero Awaiting requested review from gabemontero

Assignees

@dgoodwin dgoodwin

@adambkaplan adambkaplan

@gabemontero gabemontero

@kasturinarra kasturinarra

@Moebasim Moebasim

@jadhaj jadhaj

@pamoedom pamoedom

@gangwgr gangwgr

@kunalmemane kunalmemane

@prabhapa prabhapa

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/severity-moderate Referenced Jira bug's severity is moderate 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. 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.