Bug 2026356 - [IPI on Azure] The bootstrap machine type should be same as master
Summary: [IPI on Azure] The bootstrap machine type should be same as master
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.9
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.11.0
Assignee: Aditya Narayanaswamy
QA Contact: MayXu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-24 12:53 UTC by MayXu
Modified: 2022-08-10 10:40 UTC (History)
3 users (show)

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.
Clone Of:
Environment:
Last Closed: 2022-08-10 10:39:48 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift installer pull 5515 0 None open Bug 2026356: Fix bootstrap disk instance type 2022-01-06 15:38:15 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 10:40:25 UTC

Description MayXu 2021-11-24 12:53:19 UTC
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

Comment 3 MayXu 2022-03-03 09:36:09 UTC
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.

Comment 7 errata-xmlrpc 2022-08-10 10:39:48 UTC
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


Note You need to log in before you can comment on or make changes to this bug.