Bug 2109538 - Nutanix platform validations run at `create manifests` stage
Summary: Nutanix platform validations run at `create manifests` stage
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.11
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.12.0
Assignee: OCP Installer
QA Contact: gaoshang
Depends On:
TreeView+ depends on / blocked
Reported: 2022-07-21 13:57 UTC by Vadim Rutkovsky
Modified: 2023-01-17 19:53 UTC (History)
0 users

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2023-01-17 19:53:12 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift installer pull 6149 0 None open Bug 2109538: nutanix: allow creating manifests without Prism Central connection 2022-07-21 15:17:16 UTC
Red Hat Product Errata RHSA-2022:7399 0 None None None 2023-01-17 19:53:25 UTC

Description Vadim Rutkovsky 2022-07-21 13:57:04 UTC

$ openshift-install version



On `openshift-installer create manifests` stage a connection to Prism is made (see https://github.com/openshift/installer/blob/master/pkg/asset/installconfig/nutanix/validation.go#L15-L36=)

This make generating manifests separately impossible, which breaks Assisted Installer flow. Instead of storing sensitive user information, Assisted Installer sets fake details in install-config.yaml and asks user to update these after installation has completed. 

With validation happening on `openshift-install create manifests` phase installation process can't start with invalid credentials.

Please move this validation to ValidateForProvisioning, similar to vSphere

Comment 3 gaoshang 2022-08-24 14:41:54 UTC
This bug has been verified on OCP 4.12.0-0.nightly-2022-08-23-223922 and passed, thanks.


1, Create install-config.yaml with fake prismElements uuid
2, Run openshift-install create manifests, check installation process can start with invalid credentials

[root@preserve-sgao nutanix]# ./openshift-install create manifests --dir cluster
INFO Consuming Install Config from target directory 
FATAL failed to fetch Common Manifests: failed to fetch dependency of "Common Manifests": failed to generate asset "Infrastructure Config": fail to find the Prism Element (cluster) with uuid fake: status: 400 BAD REQUEST, error-response: { 
FATAL   "api_version": "3.1",                      
FATAL   "code": 400,                               
FATAL   "kind": "cluster",                         
FATAL   "message_list": [                          
FATAL     {                                        
FATAL       "message": "Invalid UUID passed. fake", 
FATAL       "reason": "INVALID_UUID"               
FATAL     }                                        
FATAL   ],                                         
FATAL   "state": "ERROR"                           
FATAL }                                            
[root@preserve-sgao nutanix]# ls cluster/

Comment 6 errata-xmlrpc 2023-01-17 19:53:12 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.12.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.