Bug 1662119
Summary: | Installer did not create expected cluster according to customized Manifests files | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | liujia <jiajliu> |
Component: | Installer | Assignee: | Matthew Staebler <mstaeble> |
Installer sub component: | openshift-installer | QA Contact: | Qin Ping <piqin> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | medium | ||
Priority: | medium | CC: | wking, wking |
Version: | 4.1.0 | ||
Target Milestone: | --- | ||
Target Release: | 4.1.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-06-04 10:41:28 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
liujia
2018-12-26 09:26:32 UTC
[1] will fix this. I'd hoped to land it this week, but there was a lot of install-config churn and it slipped through. [1]: https://github.com/openshift/installer/pulls/wking Oops, I'd meant to link https://github.com/openshift/installer/pull/792 https://github.com/openshift/installer/pull/890 fixes preserving changes to the manifests. https://github.com/openshift/installer/pull/1121 fixes specifying the availability zone to use for masters. https://github.com/openshift/installer/pull/1211 fixes panic when reading in the master machines manifest file in later stages. Some of these changes went out in v0.13.0 [1], but [2] is still in flight. [1]: https://github.com/openshift/installer/releases/tag/v0.13.0 [2]: https://github.com/openshift/installer/pull/1121 https://github.com/openshift/installer/pull/1121 just landed and will go out in the next release. verified with: $ ./openshift-install version ./openshift-install v4.0.21-1-dirty 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 |