Bug 1676725
| Summary: | Create ocp cluster panic with existing manifests | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Qin Ping <piqin> |
| Component: | Installer | Assignee: | Matthew Staebler <mstaeble> |
| Installer sub component: | openshift-installer | QA Contact: | Qin Ping <piqin> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | high | ||
| Priority: | high | CC: | sponnaga, wking, wsun |
| Version: | 4.1.0 | Keywords: | Regression |
| Target Milestone: | --- | ||
| Target Release: | 4.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: creating the terraform to create the aws resources attempts to access fields that are not filled in when the master machines asset is read in from the state file
Consequence: installer panics dereferencing a nil pointer
Fix: properly acquire the needed data to create the terraform for the master machines
Result: no installer panic when creating terraform
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-06-04 10:44:00 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: | |||
|
Description
Qin Ping
2019-02-13 03:18:09 UTC
Verfied with: $ ./openshift-install version ./openshift-install v4.0.0-0.175.0.0-dirty RELEASE_IMAGE: 4.0.0-0.nightly-2019-02-17-182259 RHCOS: 47.318 [1] went out with [2], so this should be fixed. [1]: https://github.com/openshift/installer/pull/1211 [2]: https://github.com/openshift/installer/releases/tag/v0.13.0 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, 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/RHBA-2019:0758 |