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

[release-4.14] OCPBUGS-51044: Add/remove team members to the OWNERS file for Builds #29554

Open
wants to merge 1 commit into
base: release-4.14
Choose a base branch
from
Open

[release-4.14] OCPBUGS-51044: Add/remove team members to the OWNERS file for Builds #29554

wants to merge 1 commit into from
+8 −2

Conversation

openshift-cherrypick-robot
Copy link

This is an automated cherry-pick of #29551

/assign prabhapa

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Feb 19, 2025
Merged
@openshift-ci-robot
Copy link

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

In response to this:

This is an automated cherry-pick of #29551

/assign prabhapa

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.14] OCPBUGS-48749: Add/remove team members to the OWNERS file for Builds [release-4.14] OCPBUGS-51044: Add/remove team members to the OWNERS file for Builds Feb 19, 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 Feb 19, 2025
@openshift-ci-robot
Copy link

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

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

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

/assign prabhapa

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.

@prabhapa
Copy link

/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 Feb 19, 2025
@openshift-ci-robot
Copy link

@prabhapa: This pull request references Jira Issue OCPBUGS-51044, 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.14.z) matches configured target version for branch (4.14.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-48749 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-48749 targets the "4.15.z" version, which is one of the valid target versions: 4.15.0, 4.15.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 openshift-eng/jira-lifecycle-plugin repository.

@prabhapa
Copy link

/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 Feb 19, 2025
@prabhapa
Copy link

/retest

@dgoodwin
Copy link
Contributor

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

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Feb 20, 2025

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

In response to this:

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

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-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 20, 2025
@Moebasim
Copy link

/lgtm

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

openshift-ci bot commented Feb 24, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dgoodwin, Moebasim, 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-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 2c640ec and 2 for PR HEAD 2d06107 in total

@prabhapa
Copy link

/retest e2e-gcp-ovn-builds

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Feb 24, 2025

@prabhapa: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

/test e2e-aws-jenkins

/test e2e-aws-ovn-fips

/test e2e-aws-ovn-image-registry

/test e2e-aws-ovn-serial

/test e2e-gcp-ovn

/test e2e-gcp-ovn-builds

/test e2e-gcp-ovn-image-ecosystem

/test e2e-gcp-ovn-upgrade

/test images

/test lint

/test unit

/test verify

/test verify-deps

The following commands are available to trigger optional jobs:

/test e2e-agnostic-ovn-cmd

/test e2e-aws

/test e2e-aws-csi

/test e2e-aws-disruptive

/test e2e-aws-etcd-recovery

/test e2e-aws-multitenant

/test e2e-aws-ovn

/test e2e-aws-ovn-cgroupsv2

/test e2e-aws-ovn-etcd-scaling

/test e2e-aws-ovn-kubevirt

/test e2e-aws-ovn-single-node

/test e2e-aws-ovn-single-node-serial

/test e2e-aws-ovn-single-node-upgrade

/test e2e-aws-ovn-upgrade

/test e2e-aws-ovn-upi

/test e2e-aws-proxy

/test e2e-azure

/test e2e-azure-ovn-etcd-scaling

/test e2e-baremetalds-kubevirt

/test e2e-gcp-csi

/test e2e-gcp-disruptive

/test e2e-gcp-fips-serial

/test e2e-gcp-ovn-etcd-scaling

/test e2e-gcp-ovn-rt-upgrade

/test e2e-gcp-ovn-techpreview

/test e2e-gcp-ovn-techpreview-serial

/test e2e-metal-ipi-ovn-dualstack

/test e2e-metal-ipi-ovn-ipv6

/test e2e-metal-ipi-sdn

/test e2e-metal-ipi-serial

/test e2e-metal-ipi-serial-ovn-ipv6

/test e2e-metal-ipi-virtualmedia

/test e2e-openstack-kuryr

/test e2e-openstack-ovn

/test e2e-openstack-serial

/test e2e-vsphere

/test e2e-vsphere-ovn-etcd-scaling

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-origin-release-4.14-e2e-agnostic-ovn-cmd

pull-ci-openshift-origin-release-4.14-e2e-aws-csi

pull-ci-openshift-origin-release-4.14-e2e-aws-etcd-recovery

pull-ci-openshift-origin-release-4.14-e2e-aws-ovn-cgroupsv2

pull-ci-openshift-origin-release-4.14-e2e-aws-ovn-fips

pull-ci-openshift-origin-release-4.14-e2e-aws-ovn-serial

pull-ci-openshift-origin-release-4.14-e2e-aws-ovn-single-node

pull-ci-openshift-origin-release-4.14-e2e-aws-ovn-single-node-serial

pull-ci-openshift-origin-release-4.14-e2e-aws-ovn-single-node-upgrade

pull-ci-openshift-origin-release-4.14-e2e-aws-ovn-upgrade

pull-ci-openshift-origin-release-4.14-e2e-gcp-csi

pull-ci-openshift-origin-release-4.14-e2e-gcp-ovn

pull-ci-openshift-origin-release-4.14-e2e-gcp-ovn-builds

pull-ci-openshift-origin-release-4.14-e2e-gcp-ovn-rt-upgrade

pull-ci-openshift-origin-release-4.14-e2e-gcp-ovn-upgrade

pull-ci-openshift-origin-release-4.14-e2e-metal-ipi-ovn-ipv6

pull-ci-openshift-origin-release-4.14-e2e-metal-ipi-sdn

pull-ci-openshift-origin-release-4.14-e2e-openstack-ovn

pull-ci-openshift-origin-release-4.14-images

pull-ci-openshift-origin-release-4.14-lint

pull-ci-openshift-origin-release-4.14-unit

pull-ci-openshift-origin-release-4.14-verify

pull-ci-openshift-origin-release-4.14-verify-deps

In response to this:

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

@prabhapa
Copy link

/test e2e-gcp-ovn-builds

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 2c640ec and 2 for PR HEAD 2d06107 in total

2 similar comments
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 2c640ec and 2 for PR HEAD 2d06107 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 2c640ec and 2 for PR HEAD 2d06107 in total

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Feb 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-aws-ovn-single-node-upgrade 2d06107 link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-etcd-recovery 2d06107 link false /test e2e-aws-etcd-recovery
ci/prow/e2e-gcp-csi 2d06107 link false /test e2e-gcp-csi
ci/prow/e2e-aws-ovn-single-node-serial 2d06107 link false /test e2e-aws-ovn-single-node-serial
ci/prow/e2e-gcp-ovn-builds 2d06107 link true /test e2e-gcp-ovn-builds

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-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 2c640ec and 2 for PR HEAD 2d06107 in total

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

@sayan-biswas sayan-biswas Awaiting requested review from sayan-biswas

Assignees

@dgoodwin dgoodwin

@adambkaplan adambkaplan

@sayan-biswas sayan-biswas

@kasturinarra kasturinarra

@Moebasim Moebasim

@jadhaj jadhaj

@pamoedom pamoedom

@prietyc123 prietyc123

@gangwgr gangwgr

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