Skip to content

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #30307

/assign wangke19

wangke19 and others added 3 commits October 30, 2025 03:32
…erType enum

Replaced three boolean flags (isHypershift, isAROHCPCluster, isBareMetalHypershift)
with a single HostedClusterType enum field for better code maintainability and
extensibility. Also added a comment explaining why ARO HCP uses port 7443.

Changes:
- Introduced HostedClusterType enum with values: Standalone, AROHCP, BareMetal, Other
- Replaced three boolean fields with single hostedClusterType field
- Updated all conditional logic to use the enum pattern
- Added comment for ARO HCP port 7443 usage
- Improved semantic clarity by aligning with HyperShift terminology

This refactoring makes it easier to add new hosted cluster types in the future
and prevents contradictory states from occurring.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 30, 2025

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: CNTRLPLANE-1485

In response to this:

This is an automated cherry-pick of #30307

/assign wangke19

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

wangke19 commented Oct 30, 2025

/retitle [release-4.19] CNTRLPLANE-1767:fix(disruption): Using correct internal LB of apiserver for monitor test on ARO and Baremetal Hypershift

@openshift-ci openshift-ci bot changed the title [release-4.19] CNTRLPLANE-1485:fix(disruption): Using correct internal LB of apiserver for monitor test on ARO and Baremetal Hypershift [release-4.19] CNTRLPLANE-1767:fix(disruption): Using correct internal LB of apiserver for monitor test on ARO and Baremetal Hypershift Oct 30, 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 Oct 30, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 30, 2025

@openshift-cherrypick-robot: This pull request references CNTRLPLANE-1767 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 bug to target either version "4.19." or "openshift-4.19.", but it targets "openshift-4.20.z" instead.

In response to this:

This is an automated cherry-pick of #30307

/assign wangke19

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

/payload-job periodic-ci-openshift-hypershift-release-4.19-periodics-mce-e2e-agent-connected-ovn-ipv4-metal-conformance

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 30, 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.19-periodics-mce-e2e-agent-connected-ovn-ipv4-metal-conformance

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/278b1cf0-b543-11f0-9a70-7d94a7493d4e-0

@wangke19
Copy link
Contributor

@wangke19
Copy link
Contributor

/verified by CI tests

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

@wangke19: This PR has been marked as verified by CI tests.

In response to this:

/verified by CI tests

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

/lgtm

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

openshift-ci bot commented Oct 31, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, wangke19
Once this PR has been reviewed and has the lgtm label, please assign sosiouxme 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

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 31, 2025

@wangke19: This pull request references CNTRLPLANE-1767 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 bug to target either version "4.19." or "openshift-4.19.", but it targets "openshift-4.20.z" instead.

In response to this:

/jira refresh

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

wangke19 commented Oct 31, 2025

/retitle [release-4.19] OCPBUGS-63727: CNTRLPLANE-1767:fix(disruption): Using correct internal LB of apiserver for monitor test on ARO and Baremetal Hypershift

@openshift-ci openshift-ci bot changed the title [release-4.19] CNTRLPLANE-1767:fix(disruption): Using correct internal LB of apiserver for monitor test on ARO and Baremetal Hypershift [release-4.19] OCPBUGS-63727: CNTRLPLANE-1767:fix(disruption): Using correct internal LB of apiserver for monitor test on ARO and Baremetal Hypershift Oct 31, 2025
@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Oct 31, 2025
@openshift-ci-robot
Copy link

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

  • expected the bug to target either version "4.19." or "openshift-4.19.", but it targets "4.20.z" instead
  • expected Jira Issue OCPBUGS-63727 to depend on a bug targeting a version in 4.20.0, 4.20.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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:

This is an automated cherry-pick of #30307

/assign wangke19

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

/jira refresh

@openshift-ci-robot
Copy link

@wangke19: This pull request references Jira Issue OCPBUGS-63727, which is invalid:

  • expected Jira Issue OCPBUGS-63727 to depend on a bug targeting a version in 4.20.0, 4.20.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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:

/jira refresh

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.

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

Labels

jira/invalid-bug Indicates that a referenced Jira bug is invalid 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.

3 participants