Skip to content

Conversation

@wangke19
Copy link
Contributor

@wangke19 wangke19 commented Sep 26, 2025

What does it do:
fix(disruption): Using correct internal LB of apiserver for monitor test on ARO and Baremetal Hypershift:
• Added new struct fields: isHypershift, isAROHCPCluster, isBareMetalHypershift
• Updated createInternalLBDeployment function to accept both apiIntHost and apiIntPort parameters
• Integrated the new logic for handling different cluster types (ARO HCP, bare metal HyperShift, standard)
• Added proper field assignments in the StartCollection function

Currently we don't have one MCE supported build for 4.21 main branch, so have to test related jobs on 4.19 and 4.20.
The related test [Jira: "kube-apiserver"] can collect apiserver.openshift.io/disruption-actor=poller poller pod logs expand_more invloved code change has been passed on AWS test and ARO test with 4.20 PR fix #30310 and Baremetal with 4.19 PR fix #30383 (something wrong with baremetal install on 4.20)

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

@wangke19
Copy link
Contributor Author

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

@openshift-ci
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

@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 15, 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:

What does it do:
fix(disruption): Using correct internal LB of apiserver for monitor test on ARO and Baremetal Hypershift:
• Added new struct fields: isHypershift, isAROHCPCluster, isBareMetalHypershift
• Updated createInternalLBDeployment function to accept both apiIntHost and apiIntPort parameters
• Integrated the new logic for handling different cluster types (ARO HCP, bare metal HyperShift, standard)
• Added proper field assignments in the StartCollection function

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.

@wangke19 wangke19 force-pushed the fix/hypershift-disruption-test branch from 5528069 to 9fb7603 Compare October 15, 2025 13:28
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 15, 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:

What does it do:
fix(disruption): Using correct internal LB of apiserver for monitor test on ARO and Baremetal Hypershift:
• Added new struct fields: isHypershift, isAROHCPCluster, isBareMetalHypershift
• Updated createInternalLBDeployment function to accept both apiIntHost and apiIntPort parameters
• Integrated the new logic for handling different cluster types (ARO HCP, bare metal HyperShift, standard)
• Added proper field assignments in the StartCollection function

Currently we don't have one MCE supported build for 4.21 main branch, so have to test related jobs on 4.19 and 4.20.

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

openshift-ci-robot commented Oct 15, 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:

What does it do:
fix(disruption): Using correct internal LB of apiserver for monitor test on ARO and Baremetal Hypershift:
• Added new struct fields: isHypershift, isAROHCPCluster, isBareMetalHypershift
• Updated createInternalLBDeployment function to accept both apiIntHost and apiIntPort parameters
• Integrated the new logic for handling different cluster types (ARO HCP, bare metal HyperShift, standard)
• Added proper field assignments in the StartCollection function

Currently we don't have one MCE supported build for 4.21 main branch, so have to test related jobs on 4.19 and 4.20.
Code change has been passed on AWS test and ARO test with 4.20 PR fix #30310 and Baremetal with 4.19 PR fix #30383

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

openshift-ci-robot commented Oct 15, 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:

What does it do:
fix(disruption): Using correct internal LB of apiserver for monitor test on ARO and Baremetal Hypershift:
• Added new struct fields: isHypershift, isAROHCPCluster, isBareMetalHypershift
• Updated createInternalLBDeployment function to accept both apiIntHost and apiIntPort parameters
• Integrated the new logic for handling different cluster types (ARO HCP, bare metal HyperShift, standard)
• Added proper field assignments in the StartCollection function

Currently we don't have one MCE supported build for 4.21 main branch, so have to test related jobs on 4.19 and 4.20.
Code change has been passed on AWS test and ARO test with 4.20 PR fix #30310 and Baremetal with 4.19 PR fix #30383

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

openshift-ci-robot commented Oct 15, 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:

What does it do:
fix(disruption): Using correct internal LB of apiserver for monitor test on ARO and Baremetal Hypershift:
• Added new struct fields: isHypershift, isAROHCPCluster, isBareMetalHypershift
• Updated createInternalLBDeployment function to accept both apiIntHost and apiIntPort parameters
• Integrated the new logic for handling different cluster types (ARO HCP, bare metal HyperShift, standard)
• Added proper field assignments in the StartCollection function

Currently we don't have one MCE supported build for 4.21 main branch, so have to test related jobs on 4.19 and 4.20.
The related code change has been passed on AWS test and ARO test with 4.20 PR fix #30310 and Baremetal with 4.19 PR fix #30383

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

openshift-ci-robot commented Oct 15, 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:

What does it do:
fix(disruption): Using correct internal LB of apiserver for monitor test on ARO and Baremetal Hypershift:
• Added new struct fields: isHypershift, isAROHCPCluster, isBareMetalHypershift
• Updated createInternalLBDeployment function to accept both apiIntHost and apiIntPort parameters
• Integrated the new logic for handling different cluster types (ARO HCP, bare metal HyperShift, standard)
• Added proper field assignments in the StartCollection function

Currently we don't have one MCE supported build for 4.21 main branch, so have to test related jobs on 4.19 and 4.20.
The related code change has been passed on AWS test and ARO test with 4.20 PR fix #30310 and Baremetal with 4.19 PR fix #30383 (something wrong with baremetal install on 4.20)

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

openshift-ci-robot commented Oct 15, 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:

What does it do:
fix(disruption): Using correct internal LB of apiserver for monitor test on ARO and Baremetal Hypershift:
• Added new struct fields: isHypershift, isAROHCPCluster, isBareMetalHypershift
• Updated createInternalLBDeployment function to accept both apiIntHost and apiIntPort parameters
• Integrated the new logic for handling different cluster types (ARO HCP, bare metal HyperShift, standard)
• Added proper field assignments in the StartCollection function

Currently we don't have one MCE supported build for 4.21 main branch, so have to test related jobs on 4.19 and 4.20.
The related test [Jira: "kube-apiserver"] can collect apiserver.openshift.io/disruption-actor=poller poller pod logs expand_more invloved code change has been passed on AWS test and ARO test with 4.20 PR fix #30310 and Baremetal with 4.19 PR fix #30383 (something wrong with baremetal install on 4.20)

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.

@wangke19 wangke19 changed the title [WIP]CNTRLPLANE-1485:fix(disruption): Skip internal LB monitor on Hypershift CNTRLPLANE-1485:fix(disruption): Using correct internal LB of apiserver for monitor test on ARO and Baremetal Hypershift Oct 15, 2025
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 15, 2025
@wangke19
Copy link
Contributor Author

/cc @LiangquanLi930

@openshift-ci openshift-ci bot requested a review from LiangquanLi930 October 15, 2025 14:11
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 15, 2025
@wangke19 wangke19 force-pushed the fix/hypershift-disruption-test branch from ec330d3 to 10c5a6d Compare October 16, 2025 04:36
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 16, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 17, 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-aws-ovn-single-node-upgrade 5528069 link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-ovn-edge-zones 5528069 link false /test e2e-aws-ovn-edge-zones
ci/prow/e2e-vsphere-ovn-upi 10c5a6d link true /test e2e-vsphere-ovn-upi
ci/prow/go-verify-deps 10c5a6d link true /test go-verify-deps

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.

@wangke19
Copy link
Contributor Author

/test go-verify-deps

@wangke19
Copy link
Contributor Author

/verified by e2e tests on AWS test , ARO test and Baremetal

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 23, 2025
@openshift-ci-robot
Copy link

@wangke19: This PR has been marked as verified by e2e tests on [AWS test](https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-origin-30310-periodics-e2e-aws-ovn-conformance/1977613953450119168),[ARO test](https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-origin-30310-periodics-e2e-azure-kubevirt-ovn/1977613994134867968) and [Baremetal](https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-origin-30383-periodics-mce-e2e-agent-connected-ovn-ipv4-metal-compact-conformance/1978394713446682624).

In response to this:

/verified by e2e tests on AWS test , ARO test and Baremetal

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.

@wangke19
Copy link
Contributor Author

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 23, 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.21-periodics-e2e-azure-aks-ovn-conformance

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/04e7b330-afcf-11f0-9a50-00a773bc37ef-0

@wangke19
Copy link
Contributor Author

/test e2e-vsphere-ovn-upi

@wangke19
Copy link
Contributor Author

/uncc @LiangquanLi930

@openshift-ci openshift-ci bot removed the request for review from LiangquanLi930 October 23, 2025 05:25
@wangke19
Copy link
Contributor Author

/cc @bryan-cox
He has made relevant tests and fixes with PR #30006

@openshift-ci openshift-ci bot requested a review from bryan-cox October 23, 2025 05:29
@wangke19
Copy link
Contributor Author

/payload 4.21 nightly blocking

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 23, 2025

@wangke19: trigger 13 job(s) of type blocking for the nightly release of OCP 4.21

  • periodic-ci-openshift-release-master-ci-4.21-e2e-aws-upgrade-ovn-single-node
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-upgrade-fips
  • periodic-ci-openshift-release-master-ci-4.21-e2e-azure-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.21-upgrade-from-stable-4.20-e2e-gcp-ovn-rt-upgrade
  • periodic-ci-openshift-hypershift-release-4.21-periodics-e2e-aws-ovn-conformance
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-serial-1of2
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-serial-2of2
  • periodic-ci-openshift-release-master-ci-4.21-e2e-aws-ovn-techpreview
  • periodic-ci-openshift-release-master-ci-4.21-e2e-aws-ovn-techpreview-serial-1of3
  • periodic-ci-openshift-release-master-ci-4.21-e2e-aws-ovn-techpreview-serial-2of3
  • periodic-ci-openshift-release-master-ci-4.21-e2e-aws-ovn-techpreview-serial-3of3
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-metal-ipi-ovn-bm
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-metal-ipi-ovn-ipv6

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/14b2f1f0-afd2-11f0-91d3-d699c4cf2bec-0

@wangke19
Copy link
Contributor Author

wangke19 commented Oct 23, 2025

From the following completed CI jobs, we can see that the monitor test [Jira: "kube-apiserver"] can collect apiserver.openshift.io/disruption-actor=poller poller pod logs expand_more has passed, so far so good, it's ready for review.

https://prow.ci.openshift.org/view/gs/test-platform-results/logs/aggregator-periodic-ci-openshift-hypershift-release-4.21-periodics-e2e-aws-ovn-conformance/1981233103720419328
https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-origin-30307-nightly-4.21-e2e-aws-ovn-serial-1of2/1981233042475192320
https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-origin-30307-nightly-4.21-e2e-aws-ovn-serial-2of2/1981233044157108224
https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-origin-30307-ci-4.21-e2e-aws-ovn-techpreview/1981233044995969024
https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-origin-30307-ci-4.21-e2e-aws-ovn-techpreview-serial-2of3/1981233048355606528
https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-origin-30307-nightly-4.21-e2e-metal-ipi-ovn-bm/1981233050012356608
https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-origin-30307-nightly-4.21-e2e-metal-ipi-ovn-ipv6/1981233050851217408
https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-origin-30307-ci-4.21-e2e-aws-ovn-techpreview-serial-1of3/1981233045822246912

@bryan-cox
Copy link
Member

/approve

@wangke19
Copy link
Contributor Author

/cc @dgoodwin
Please help to approve.

@openshift-ci openshift-ci bot requested a review from dgoodwin October 23, 2025 14:26
@bryan-cox
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 23, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 23, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: bryan-cox, 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

/uncc @dgoodwin
/cc @smg247

@openshift-ci openshift-ci bot requested review from smg247 and removed request for dgoodwin October 24, 2025 05:02

adminRESTConfig *rest.Config
kubeClient kubernetes.Interface
isHypershift bool
Copy link
Contributor

@neisw neisw Oct 24, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of 3 hypershift specific fields could a ControlPlaneType or HostedClusterType or some more generic field be added so that there is only one new field that might be reused in other cases as added.

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

Labels

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.

5 participants