OCPBUGS-6938: [release-4.8] Clean up admins

[openshift-cherrypick-robot]

This is an automated cherry-pick of #294

/assign everettraven

[everettraven]

/retitle OCPBUGS-6938: [release-4.8] Clean up admins

[openshift-ci-robot]

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

• expected the bug to target the "4.8.z" version, but no target version was set
• expected dependent Jira Issue OCPBUGS-6937 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is New instead
• expected dependent Jira Issue OCPBUGS-6937 to target a version in 4.9.0, 4.9.z, but no target version was set

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](https://github.com/openshift/ocp-release-operator-sdk/pull/301): >This is an automated cherry-pick of #294 > >/assign everettraven Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[openshift-ci[bot]]

@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](https://github.com/openshift/ocp-release-operator-sdk/pull/301): >OCPBUGS-6938: [release-4.8] Clean up admins Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[oceanc80]

/label backport-risk-assessed

[oceanc80]

/lgtm

[everettraven]

/jira refresh

[openshift-ci-robot]

@everettraven: This pull request references Jira Issue OCPBUGS-6938, which is invalid:

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

In response to [this](https://github.com/openshift/ocp-release-operator-sdk/pull/301#issuecomment-1432025018): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

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

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: - ~~[OWNERS](https://github.com/openshift/ocp-release-operator-sdk/blob/release-4.8/OWNERS)~~ [varshaprasad96] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[oceanc80]

/jira refresh

[openshift-ci-robot]

@oceanc80: This pull request references Jira Issue OCPBUGS-6938, which is invalid:

• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA 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.

In response to [this](https://github.com/openshift/ocp-release-operator-sdk/pull/301#issuecomment-1432333624): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[emmajiafan]

/jira refresh

[openshift-ci-robot]

@emmajiafan: This pull request references Jira Issue OCPBUGS-6938, which is valid.

6 validation(s) were run on this bug

* bug is open, matching expected state (open) * bug target version (4.8.z) matches configured target version for branch (4.8.z) * bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST) * dependent bug [Jira Issue OCPBUGS-6937](https://issues.redhat.com//browse/OCPBUGS-6937) is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE)) * dependent [Jira Issue OCPBUGS-6937](https://issues.redhat.com//browse/OCPBUGS-6937) targets the "4.9.z" version, which is one of the valid target versions: 4.9.0, 4.9.z * bug has dependents

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

In response to [this](https://github.com/openshift/ocp-release-operator-sdk/pull/301#issuecomment-1432355834): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[emmajiafan]

/label cherry-pick-approved

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD ac914026d53a5d61da601256d1d822ccb0abd9a4 and 2 for PR HEAD 35c48937464aaf610e94666e80b94fb5fc4668b3 in total

[openshift-ci[bot]]

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).

[openshift-ci-robot]

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

• openshift/ocp-release-operator-sdk#301

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

In response to [this](https://github.com/openshift/ocp-release-operator-sdk/pull/301): >This is an automated cherry-pick of #294 > >/assign everettraven Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[openshift-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build openshift-enterprise-operator-sdk-container-v4.8.0-202311261141.p0.ga4b5df6.assembly.stream for distgit openshift-enterprise-operator-sdk. All builds following this will include this PR.