OCPBUGS-63028: filtering only PEs from cluster list

[abhay-nutanix]

Problem
The OpenShift installer fails with the following error when creating an install-config for Nutanix environments where Prism Central and Prism Element clusters share the same name:
FATAL failed to fetch Install Config: failed to fetch dependency of "Install Config": failed to fetch dependency of "Base Domain": failed to generate asset "Platform": missing ExternalIP in Prism Element network spec for "Development-LTS2"

Root Cause
The Nutanix v3 API's ListAllCluster endpoint returns both Prism Element (PE) and Prism Central (PC) clusters. The installer's getPrismElement() function did not distinguish between these cluster types.
If a Prism Element and Prism Central share the same name, the Prism Central entry overwrites the Prism Element entry in the map. Since Prism Central clusters typically don't have an ExternalIP configured in their network specification, selecting that cluster results in the "missing ExternalIP" error.

Solution
Modified pkg/asset/installconfig/nutanix/nutanix.go to filter out Prism Central clusters before presenting options to the user. The filtering logic:
Inspects the service_list field in each cluster's status
Excludes any cluster with "PRISM_CENTRAL" in its service list
Only presents Prism Element clusters (those with "AOS" or other non-PC services)
The implementation includes defensive nil checks to handle clusters with incomplete metadata gracefully.

[openshift-ci-robot]

@abhay-nutanix: This pull request references Jira Issue OCPBUGS-63028, which is invalid:

• expected the bug to target the "4.22.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.

Details

In response to this:

Problem
The OpenShift installer fails with the following error when creating an install-config for Nutanix environments where Prism Central and Prism Element clusters share the same name:
FATAL failed to fetch Install Config: failed to fetch dependency of "Install Config": failed to fetch dependency of "Base Domain": failed to generate asset "Platform": missing ExternalIP in Prism Element network spec for "Development-LTS2"

Root Cause
The Nutanix v3 API's ListAllCluster endpoint returns both Prism Element (PE) and Prism Central (PC) clusters. The installer's getPrismElement() function did not distinguish between these cluster types.
If a Prism Element and Prism Central share the same name, the Prism Central entry overwrites the Prism Element entry in the map. Since Prism Central clusters typically don't have an ExternalIP configured in their network specification, selecting that cluster results in the "missing ExternalIP" error.

Solution
Modified pkg/asset/installconfig/nutanix/nutanix.go to filter out Prism Central clusters before presenting options to the user. The filtering logic:
Inspects the service_list field in each cluster's status
Excludes any cluster with "PRISM_CENTRAL" in its service list
Only presents Prism Element clusters (those with "AOS" or other non-PC services)
The implementation includes defensive nil checks to handle clusters with incomplete metadata gracefully.

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.

[abhay-nutanix]

/jira refresh

[openshift-ci-robot]

@abhay-nutanix: This pull request references Jira Issue OCPBUGS-63028, 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.22.0) matches configured target version for branch (4.22.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @gpei

Details

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.

[abhay-nutanix]

/retest-required

[sgaoshang]

/verified by @sgaoshang

[openshift-ci-robot]

@sgaoshang: /verified by <reason> requires at least one verification method to be identified (it can be a comma delimited list). It can specify a test name or a GitHub @username (an engineer that performed the pre-merge verification). See https://docs.ci.openshift.org/docs/architecture/jira/#premerge-verification for more information.

Details

In response to this:

/verified by @sgaoshang

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.

[abhay-nutanix]

/retest

[openshift-ci]

@abhay-nutanix: 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-nutanix-ovn	ea74870	link	false	/test e2e-nutanix-ovn
ci/prow/okd-scos-images	ea74870	link	true	/test okd-scos-images

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.

[jcpowermac]

@abhay-nutanix the cluster didn't bootstrap and you confirm that this pr isn't the cause, thanks!

[jcpowermac]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jcpowermac

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:

• pkg/asset/installconfig/nutanix/OWNERS [jcpowermac]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment