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

[openshift-cherrypick-robot]

This is an automated cherry-pick of #29608

/assign kunalmemane

[openshift-ci-robot]

@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-robot]

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

/retest
/jira refresh

[openshift-ci-robot]

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

/approve
/lgtm

[openshift-ci]

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

• test/extended/builds/OWNERS [gabemontero]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kunalmemane]

/retest

[kunalmemane]

/test e2e-gcp-ovn-builds

[openshift-ci]

@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-gcp-ovn-rt-upgrade	23d2495	link	false	/test e2e-gcp-ovn-rt-upgrade
ci/prow/e2e-gcp-ovn-builds	23d2495	link	true	/test e2e-gcp-ovn-builds
ci/prow/e2e-aws-ovn-upgrade	23d2495	link	false	/test e2e-aws-ovn-upgrade
ci/prow/e2e-gcp-csi	23d2495	link	false	/test e2e-gcp-csi
ci/prow/e2e-agnostic-ovn-cmd	23d2495	link	false	/test e2e-agnostic-ovn-cmd
ci/prow/e2e-aws-ovn-single-node-serial	23d2495	link	false	/test e2e-aws-ovn-single-node-serial

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.