Bug 2050767
| Summary: | Vsphere upi tries to access vsphere during manifests generation phase | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Yuri Obshansky <yobshans> |
| Component: | Installer | Assignee: | Nobody <nobody> |
| Installer sub component: | openshift-installer | QA Contact: | jima |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | medium | CC: | padillon, rbost, rfreiman |
| Version: | 4.10 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.11.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: on vsphere validation was added to check for the existence of a network during creation of configuration files
Consequence: upi or other installation methods which may provision infrastructure after config file generation received an error
Fix: move validation to only be done when creating a cluster with IPI
Result: UPI and other install methods can generate config files with networks that do not exist yet
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-08-10 10:47:24 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2050801 | ||
|
Description
Yuri Obshansky
2022-02-04 15:33:31 UTC
Works well with 4.9.* Probably it is related to https://github.com/openshift/installer/blob/release-4.10/pkg/asset/installconfig/vsphere/validation.go#L29-L32 Slack discussion https://coreos.slack.com/archives/CH06KMDRV/p1643926906572139 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. https://access.redhat.com/errata/RHSA-2022:5069 |