Skip to content

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #489

/assign openshift-cherrypick-robot

@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-72509 has been cloned as Jira Issue OCPBUGS-72563. Will retitle bug to link to clone.
/retitle [release-4.20] OCPBUGS-72563: deploy prometheus role and binding on hypershift guest

Details

In response to this:

This is an automated cherry-pick of #489

/assign openshift-cherrypick-robot

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.20] OCPBUGS-72509: deploy prometheus role and binding on hypershift guest [release-4.20] OCPBUGS-72563: deploy prometheus role and binding on hypershift guest Jan 10, 2026
@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 Jan 10, 2026
@openshift-ci-robot
Copy link

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

  • expected dependent Jira Issue OCPBUGS-72509 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.

Details

In response to this:

This is an automated cherry-pick of #489

/assign openshift-cherrypick-robot

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.

@dobsonj
Copy link
Member

dobsonj commented Jan 10, 2026

/lgtm
/approve
/label backport-risk-assessed
/payload-job periodic-ci-openshift-hypershift-release-4.22-periodics-e2e-azure-aks-ovn-conformance

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jan 10, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 10, 2026

@dobsonj: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-hypershift-release-4.22-periodics-e2e-azure-aks-ovn-conformance

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/25b7c8a0-edcf-11f0-979b-9d55a489c771-0

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 10, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 10, 2026

[APPROVALNOTIFIER] This PR is APPROVED

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

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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 Jan 10, 2026
@dobsonj
Copy link
Member

dobsonj commented Jan 10, 2026

/payload-job periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-azure-aks-ovn-conformance

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 10, 2026

@dobsonj: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-azure-aks-ovn-conformance

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/48dc0f80-edcf-11f0-999c-bc8e39b0b522-0

@duanwei33
Copy link
Contributor

/payload-job periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-azure-aks-ovn-conformance

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 11, 2026

@duanwei33: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-azure-aks-ovn-conformance

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/bb9ae860-ee93-11f0-9960-9ab74016b47d-0

@duanwei33
Copy link
Contributor

/retest

@duanwei33
Copy link
Contributor

/unassign @Phaow @chao007 @radeore

@openshift-ci openshift-ci bot unassigned chao007 and Phaow Jan 12, 2026
@dobsonj
Copy link
Member

dobsonj commented Jan 12, 2026

from azure-disk-csi-driver-operator log:

I0111 02:57:17.696116 1 event.go:377] Event(v1.ObjectReference{Kind:"Deployment", Namespace:"openshift-cluster-csi-drivers", Name:"azure-disk-csi-driver-operator", UID:"27ef40fb-8077-45fa-a04a-b18c5936fa3a", APIVersion:"apps/v1", ResourceVersion:"", FieldPath:""}): type: 'Normal' reason: 'RoleCreated' Created Role.rbac.authorization.k8s.io/azure-disk-csi-driver-prometheus -n openshift-cluster-csi-drivers because it was missing

I0111 02:57:19.596355 1 event.go:377] Event(v1.ObjectReference{Kind:"Deployment", Namespace:"openshift-cluster-csi-drivers", Name:"azure-disk-csi-driver-operator", UID:"27ef40fb-8077-45fa-a04a-b18c5936fa3a", APIVersion:"apps/v1", ResourceVersion:"", FieldPath:""}): type: 'Normal' reason: 'RoleBindingCreated' Created RoleBinding.rbac.authorization.k8s.io/azure-disk-csi-driver-prometheus -n openshift-cluster-csi-drivers because it was missing

/verified by payload-job
/retest-required

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jan 12, 2026
@openshift-ci-robot
Copy link

@dobsonj: This PR has been marked as verified by payload-job.

Details

In response to this:

from azure-disk-csi-driver-operator log:

I0111 02:57:17.696116 1 event.go:377] Event(v1.ObjectReference{Kind:"Deployment", Namespace:"openshift-cluster-csi-drivers", Name:"azure-disk-csi-driver-operator", UID:"27ef40fb-8077-45fa-a04a-b18c5936fa3a", APIVersion:"apps/v1", ResourceVersion:"", FieldPath:""}): type: 'Normal' reason: 'RoleCreated' Created Role.rbac.authorization.k8s.io/azure-disk-csi-driver-prometheus -n openshift-cluster-csi-drivers because it was missing

I0111 02:57:19.596355 1 event.go:377] Event(v1.ObjectReference{Kind:"Deployment", Namespace:"openshift-cluster-csi-drivers", Name:"azure-disk-csi-driver-operator", UID:"27ef40fb-8077-45fa-a04a-b18c5936fa3a", APIVersion:"apps/v1", ResourceVersion:"", FieldPath:""}): type: 'Normal' reason: 'RoleBindingCreated' Created RoleBinding.rbac.authorization.k8s.io/azure-disk-csi-driver-prometheus -n openshift-cluster-csi-drivers because it was missing

/verified by payload-job
/retest-required

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
Copy link
Contributor

openshift-ci bot commented Jan 12, 2026

@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-azurestack-csi 2418872 link false /test e2e-azurestack-csi
ci/prow/e2e-openstack 2418872 link false /test e2e-openstack

Full PR test history. Your PR dashboard.

Details

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.

@Phaow
Copy link
Contributor

Phaow commented Jan 13, 2026

/retest-required

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

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. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. 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. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants