Bug 2038384 - Azure Default Instance Types are Incorrect
Summary: Azure Default Instance Types are Incorrect
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: aos-install
QA Contact: MayXu
Depends On:
Blocks: 2038429
TreeView+ depends on / blocked
Reported: 2022-01-07 18:57 UTC by Patrick Dillon
Modified: 2022-03-10 16:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-03-10 16:37:38 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift installer pull 5519 0 None open Bug 2038384: Azure: Update Default Instance Types 2022-01-07 19:01:40 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:37:54 UTC

Comment 3 MayXu 2022-01-10 03:16:24 UTC
checked IPI on Azure with 4.10.0-0.nightly-2022-01-08-215919
$ az vm list -g $RG --query "[].[name,hardwareProfile.vmSize,provisioningState]" -o tsv
maxu2038384-hl4x9-master-0	Standard_D8s_v3	Succeeded
maxu2038384-hl4x9-master-1	Standard_D8s_v3	Succeeded
maxu2038384-hl4x9-master-2	Standard_D8s_v3	Succeeded
maxu2038384-hl4x9-worker-northcentralus-7cdh9	Standard_D4s_v3	Succeeded
maxu2038384-hl4x9-worker-northcentralus-9g2vk	Standard_D4s_v3	Succeeded
maxu2038384-hl4x9-worker-northcentralus-mqjf9	Standard_D4s_v3	Succeeded

Comment 4 MayXu 2022-01-27 11:07:42 UTC
ASH check with release:4.10.0-0.nightly-2022-01-25-023600 
master : Standard_DS4_v2  (28 Gib)
worker : Standard_DS3_v2

Comment 7 errata-xmlrpc 2022-03-10 16:37:38 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.