Thanks for opening a bug report!
Before hitting the button, please fill in as much of the template below as you can.
If you leave out information, it's harder to help you.
Be ready for follow-up questions, and please respond in a timely manner.
If we can't reproduce a bug we might close your issue.
If we're wrong, PLEASE feel free to reopen it and explain why.
$ openshift-install version
#Please specify the platform type: aws, libvirt, openstack or baremetal etc.
UPI (semi-manual installation on customized infrastructure)
Cannot install Openshift cluster using Assisted Service cloud solution.
The procedure stacked on error "2/3/2022, 5:09:01 PM warning Failed to prepare the installation due to an unexpected error: failed generating install config for cluster d3feaa8a-d855-4ca8-a0c8-5b3127535210: error running openshift-install manifests, level=fatal msg=failed to fetch Master Machines: failed to load asset "Install Config": platform.vsphere: Internal error: unable to connect to vCenter vcenterplaceholder.: Post "https://vcenterplaceholder/sdk": dial tcp: lookup vcenterplaceholder on 10.120.0.10:53: no such host : exit status 1. Please retry later"
More details Jira ticket https://issues.redhat.com/browse/MGMT-9170
# Always at least include the `.openshift_install.log`
What did you expect to happen?
#Enter text here.
How to reproduce it (as minimally and precisely as possible)?
Anything else we need to know?
#Enter text here.
Works well with 4.9.*
Probably it is related to
Validation behavior has been changed from 4.9 to 4.10
I am lowering the severity of this. The installer does not support using an install-config.yaml with invalid values for the vCenter.
Reproduced the issue on 4.10.0-0.nightly-2022-02-07-162517.
Set invalid vCenter in install-config.yaml, then run command:
$ ./openshift-install create manifests --dir upi
FATAL failed to fetch Master Machines: failed to load asset "Install Config": platform.vsphere: Internal error: unable to connect to vCenter vcenter1.sddc.vmwarevmc.com.: Post "https://vcenter1.sddc.vmwarevmc.com/sdk": dial tcp: lookup vcenter1.sddc-44-236-21-251.vmwarevmc.com on 10.0.0.2:53: no such host
Verified on 4.11.0-0.nightly-2022-02-07-154612.
Set valid vCenter in install-config.yaml, then run command:
$ ./openshift-install create manifests --dir upi/
INFO Consuming Install Config from target directory
WARNING Making control-plane schedulable by setting MastersSchedulable to true for Scheduler cluster settings
INFO Manifests created in: upi/manifests and upi/openshift
$ ./openshift-install create ignition-configs --dir upi
INFO Consuming Master Machines from target directory
INFO Consuming Worker Machines from target directory
INFO Consuming Openshift Manifests from target directory
INFO Consuming OpenShift Install (Manifests) from target directory
INFO Consuming Common Manifests from target directory
INFO Ignition-Configs created in: upi and upi/auth
Also checked that invalid network checking still works well during provisioning infrastructure for IPI installation.
$ ./openshift-install create cluster --dir ipi
INFO Consuming Worker Ignition Config from target directory
INFO Consuming Master Ignition Config from target directory
INFO Consuming Bootstrap Ignition Config from target directory
FATAL failed to fetch Terraform Variables: failed to fetch dependency of "Terraform Variables": failed to generate asset "Platform Provisioning Check": platform.vsphere.network: Invalid value: "qe-segment11": unable to find network provided
The issue successfully verified on 4.10.0-rc.6
The bug can be closed
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 (Important: OpenShift Container Platform 4.11.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.