Bug 2026356
| Summary: | [IPI on Azure] The bootstrap machine type should be same as master | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | MayXu <maxu> |
| Component: | Installer | Assignee: | Aditya Narayanaswamy <anarayan> |
| Installer sub component: | openshift-installer | QA Contact: | MayXu <maxu> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | low | ||
| Priority: | low | CC: | anarayan, jialiu, maxu |
| Version: | 4.9 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.11.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: The bootstrap nodes were using hard coded default values for the instance type
Consequences: Dynamic user input was disregarded
Fix: Taking the configuration for the control plane and replicating it for the bootstrap nodes
Result: User input determines the bootstrap node instance type.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-08-10 10:39:48 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: | |||
verified on azure with registry.ci.openshift.org/ocp/release:4.11.0-0.nightly-2022-03-03-061758 the bootstap vm is same as the master nodes. 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 |
Version: $ openshift-install version openshift-install 4.9.0-0.nightly-2021-11-22-163611 built from commit 1c538b8949f3a0e5b993e1ae33b9cd799806fa93 release image registry.ci.openshift.org/ocp/release@sha256:fe24e3d144e10d481076cac138a9ed8b6ecb1e3d3b25b5e3f2c91e49c2b03552 release architecture amd64 Platform: Azure Please specify: IPI What happened? IPI on Azure, bootstrap VM size is not same as master How to reproduce it (as minimally and precisely as possible)? 1.$openshift-install create install-config <installFolder> Specify the master vm in install-config.yaml as the following: name: master platform: azure: type: Standard_D8s_v3 2.$openshift-install create cluster --dir <installFolder> 3.need not waiting for the install completed, check the bootstrap vm size on portal https://portal.azure.com/#blade/HubsExtension/BrowseResource/resourceType/Microsoft.Compute%2FVirtualMachines *Actual results:* bootstrap VM size is Standard_D4s_v3 What did you expect to happen? bootstrap VM size is same as master's size which specified in the install-config.yaml Anything else we need to know? On AWS, have similar issues 4.10 Bug 2016955 m5.large instance type for bootstrap node is hardcoded causing deployments to fail if instance type is not available 4.9 Bug 2017985 m5.large instance type for bootstrap node is hardcoded causing deployments to fail if instance type is not available 4.8 Bug 2017986 m5.large instance type for bootstrap node is hardcoded causing deployments to fail if instance type is not available