Bug 2026321 - [UPI on Azure] Shall we remove allowedValue about VMSize in ARM templates
Summary: [UPI on Azure] Shall we remove allowedValue about VMSize in ARM templates
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.9
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: Aditya Narayanaswamy
QA Contact: MayXu
Depends On:
TreeView+ depends on / blocked
Reported: 2021-11-24 11:18 UTC by MayXu
Modified: 2022-03-12 04:39 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
The values for VMSize that are allowed are mentioned in the ARM templates for Azure UPI which looks like an extra overhead on the team to constantly update it everytime Azure adds/modifies the VMSize values. Removing the allowedValues field and recommending the user to provide the minimum requirement for a VM in the docs should be a better solution.
Clone Of:
Last Closed: 2022-03-12 04:39:01 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift installer pull 5532 0 None open Bug 2026321: Remove allowed values for nodeVMsize 2022-01-12 14:36:14 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-12 04:39:16 UTC

Description MayXu 2021-11-24 11:18:50 UTC

$ 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



Please specify:

What happened?

Not each of the VM size in the allowedValue of VM Size in ARM templates work, and not all of the allowed VM Size are listed.

such as Standard_A2 are PremiumIO=false, can no be used.

What did you expect to happen?

list the vm sizes which we can used in doc
For Azure, the vm size needs to match the following: 
1. PremiumIO=true
2. HyperVGenerations Contains 'V1'
3. vCPUsAvailable and  MemoryGB meet the following minimum requirements: 
worker VM: 4 vCPUsAvaliable, 8GB Memory
master VM: 8 vCPUsAvaliable, 16GB Memory

How to reproduce it (as minimally and precisely as possible)?

Based on https://docs.openshift.com/container-platform/4.9/installing/installing_azure/installing-azure-user-infra.html
Specify the bootstrapVMSize parameter with "Standard_A2" in 04_bootstrap.json ARM template https://docs.openshift.com/container-platform/4.9/installing/installing_azure/installing-azure-user-infra.html#installation-arm-bootstrap_installing-azure-user-infra

az deployment group create -g $RESOURCE_GROUP --template-file "04_bootstrap.json" --parameters bootstrapIgnition="$BOOTSTRAP_IGNITION" --parameters sshKeyData="$SSH_KEY"   --parameters baseName="$INFRA_ID" --parameters bootstrapVMSize="Standard_A2" --verbose

Got the following error:
{"status":"Failed","error":{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"BadRequest","message":"{\r\n  \"error\": {\r\n    \"code\": \"InvalidParameter\",\r\n    \"message\": \"Requested operation cannot be performed because the VM size Standard_A2 does not support the storage account type Premium_LRS of disk 'maxupr-fhk9c-bootstrap_OSDisk'. Consider updating the VM to a size that supports Premium storage.\",\r\n    \"target\": \"osDisk.managedDisk.storageAccountType\"\r\n  }\r\n}"}]}}

Anything else we need to know?

Suggest fix as AWS: https://github.com/openshift/installer/pull/5166

Comment 6 errata-xmlrpc 2022-03-12 04:39:01 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 (Moderate: OpenShift Container Platform 4.10.3 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.


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