Skip to content

Conversation

wangke19
Copy link
Contributor

The internal load balancer monitor is not applicable to Hypershift clusters and causes test failures. This change skips the deployment of the internal LB monitor on Hypershift.

The internal load balancer monitor is not applicable to Hypershift
clusters and causes test failures. This change skips the deployment
of the internal LB monitor on Hypershift.
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 26, 2025
@wangke19 wangke19 changed the title [WIP]fix(disruption): Skip internal LB monitor on Hypershift [WIP]CNTRLPLANE-1485:fix(disruption): Skip internal LB monitor on Hypershift Sep 26, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 26, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 26, 2025

@wangke19: This pull request references CNTRLPLANE-1485 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.21.0" version, but no target version was set.

In response to this:

The internal load balancer monitor is not applicable to Hypershift clusters and causes test failures. This change skips the deployment of the internal LB monitor on Hypershift.

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.

Copy link
Contributor

openshift-ci bot commented Sep 26, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: wangke19
Once this PR has been reviewed and has the lgtm label, please assign smg247 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@wangke19
Copy link
Contributor Author

/payload-job periodic-ci-openshift-hypershift-release-4.20-periodics-mce-e2e-agent-disconnected-ovn-dualstack-metal-conformance

Copy link
Contributor

openshift-ci bot commented Sep 26, 2025

@wangke19: 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-mce-e2e-agent-disconnected-ovn-dualstack-metal-conformance

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/61cb0080-9ad9-11f0-880c-01ec80b2888e-0

Copy link
Contributor

openshift-ci bot commented Oct 3, 2025

@wangke19: 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-cgroupsv2 5528069 link false /test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-aws-ovn-single-node 5528069 link false /test e2e-aws-ovn-single-node
ci/prow/e2e-gcp-ovn 5528069 link true /test e2e-gcp-ovn
ci/prow/e2e-aws-ovn-single-node-upgrade 5528069 link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-ovn-serial-2of2 5528069 link true /test e2e-aws-ovn-serial-2of2
ci/prow/okd-scos-e2e-aws-ovn 5528069 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-edge-zones 5528069 link false /test e2e-aws-ovn-edge-zones
ci/prow/e2e-aws-ovn-microshift-serial 5528069 link true /test e2e-aws-ovn-microshift-serial
ci/prow/e2e-aws-csi 5528069 link true /test e2e-aws-csi
ci/prow/e2e-gcp-csi 5528069 link true /test e2e-gcp-csi

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants