OCPBUGS-18969: move pruner role creation from openshift-apiserver

[flavianmissi]

Needs to be tested together with openshift/openshift-apiserver#391.
I'm not sure how to reproduce the associated bug, it's intermittent and seems related to the pruner running during the upgrade. I'd be satisfied with running regression tests for this and if the bug is seen again allow users to reopen the Jira ticket.

[openshift-ci-robot]

@flavianmissi: This pull request references Jira Issue OCPBUGS-18969, which is invalid:

• expected the bug to target the "4.15.0" version, 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:

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

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

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.15.0) matches configured target version for branch (4.15.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @wewang58

In response to this:

Needs to be tested together with openshift/openshift-apiserver#391

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

@flavianmissi: This pull request references Jira Issue OCPBUGS-18969, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.15.0) matches configured target version for branch (4.15.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @wewang58

In response to this:

Needs to be tested together with openshift/openshift-apiserver#391.
I'm not sure how to reproduce the associated bug, it's intermittent and seems related to the pruner running during the upgrade. I'd be satisfied with running regression tests for this and if the bug is seen again allow users to reopen

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.

[flavianmissi]

/retest

[flavianmissi]

/retest

[flavianmissi]

/retest

[flavianmissi]

/retest

[flavianmissi]

/retest

[openshift-ci]

@flavianmissi: all tests passed!

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/test-infra repository. I understand the commands that are listed here.

[dmage]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dmage, flavianmissi

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 [dmage,flavianmissi]

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]

@flavianmissi: Jira Issue OCPBUGS-18969: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

• openshift/openshift-apiserver#391 is open

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

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

In response to this:

Needs to be tested together with openshift/openshift-apiserver#391.
I'm not sure how to reproduce the associated bug, it's intermittent and seems related to the pruner running during the upgrade. I'd be satisfied with running regression tests for this and if the bug is seen again allow users to reopen the Jira ticket.

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]

Fix included in accepted release 4.15.0-0.nightly-2023-10-09-101435