Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2085380

Summary:	[IPI-Azure] Incorrect error prompt validate VM image and instance HyperV gen match when install cluster
Product:	OpenShift Container Platform	Reporter:	MayXu <maxu>
Component:	Installer	Assignee:	Rafael Fonseca <rdossant>
Installer sub component:	openshift-installer	QA Contact:	MayXu <maxu>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	low
Priority:	low	CC:	anarayan, mifiedle, rdossant
Version:	4.11
Target Milestone:	---
Target Release:	4.11.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-08-10 11:11:36 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 MayXu 2022-05-13 08:05:37 UTC

Version: registry.ci.openshift.org/ocp/release:4.11.0-0.nightly-2022-05-11-054135
How reproducible:
always

Steps to Reproduce:
In install-config.yaml, specify the compute vm type with HyperVGenerations ==’V2’
type: Standard_DC4s_v3
osImage:
  publisher: redhat
  offer: ocp-worker
  sku: ocp-worker-c-gen1
  version: 4.8.2021122100
Create cluster failed with the following :


level=error msg="failed to fetch Master Machines: failed to load asset \"Install Config\": failed to create install config: controlPlane.platform.azure.type: Invalid value: \"Standard_DC8s_v3\": capability not found: PremiumIO"

Expected: the error message is more clear : the  VM generation of VM does not match with the VM generation of Image.

Comment 1 Aditya Narayanaswamy 2022-05-16 13:37:07 UTC

Can you show the compute node section of the install-config? This does not look like a Hyper-V generation error but a PremiumIO error. Compute nodes also need PremiumIO capability in the instance type selected along with the V2 version as our recommendations for the compute nodes include Premium disk capability so you need to pick another instance type with both the capabilities for testing. From the error message, it looks like you are picking "Standard_DC8s_v3" which I guess does not support PremiumIO capability for the region you selected.

Comment 2 Rafael Fonseca 2022-05-16 14:32:27 UTC

(In reply to Aditya Narayanaswamy from comment #1)
> Can you show the compute node section of the install-config? This does not
> look like a Hyper-V generation error but a PremiumIO error. Compute nodes
> also need PremiumIO capability in the instance type selected along with the
> V2 version as our recommendations for the compute nodes include Premium disk
> capability so you need to pick another instance type with both the
> capabilities for testing. From the error message, it looks like you are
> picking "Standard_DC8s_v3" which I guess does not support PremiumIO
> capability for the region you selected.

This error is a result of commit https://github.com/openshift/installer/commit/baabb7daa3d8133a750a1f1fc04fb910c11d00df which changed the way the instance capabilities are checked. Before that, we were looping through the present capabilities and validating each one of them. So if some capability was not present, it was silently ignored during validation. With those changes, the capabilities are now accessed directly and validation fails if one of the capabilities is not found.

Comment 3 MayXu 2022-05-16 15:11:21 UTC

apiVersion: v1
controlPlane:
  architecture: amd64
  hyperthreading: Enabled
  name: master
  platform:
    azure:
      type: Standard_DC8s_v3
      osDisk:
        diskSizeGB: 256
        diskType: StandardSSD_LRS
  replicas: 3
compute:
- architecture: amd64
  hyperthreading: Enabled
  name: worker
  platform:
    azure:
      type: Standard_DC4s_v3
      osDisk:
        diskSizeGB: 256
        diskType: Premium_LRS
      vmNetworkingType: Basic
      osImage:
        publisher: redhat
        offer: ocp-worker
        sku: ocp-worker-c-gen1
        version: 4.8.2021122100
  replicas: 2
metadata:
  name: maxu-hym1
platform:
  azure:
    region: eastus2
    baseDomainResourceGroupName: os4-common
pullSecret: HIDDEN
networking:
  clusterNetwork:
  - cidr: 10.128.0.0/14
    hostPrefix: 23
  serviceNetwork:
  - 172.30.0.0/16
  machineNetwork:
  - cidr: 10.0.0.0/16
  networkType: OpenShiftSDN
publish: External
baseDomain: qe.azure.devcluster.openshift.com

Comment 5 MayXu 2022-06-06 03:57:00 UTC

verified on registry.ci.openshift.org/ocp/release:4.11.0-0.nightly-2022-06-05-215804

Comment 7 errata-xmlrpc 2022-08-10 11:11:36 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