Bug 2025868
Summary: | [IPI on azure] Pre-check on IPI Azure, should check whether the VM Size’s HyperVGenerations contains ‘V1’ for the sku. | ||
---|---|---|---|
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: | medium | CC: | anarayan, gpei, jialiu, maxu, mstaeble, padillon |
Version: | 4.9 | ||
Target Milestone: | --- | ||
Target Release: | 4.10.z | ||
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-03-21 12:40:05 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
2021-11-23 09:10:29 UTC
Trying to establish some background on this. My take is: Azure supports gen1 & gen2 VMs. Typically you create a gen2 VM by selecting a gen2 compatible instance type (for example a Standard D4s v3 is both gen1 & gen2 compatible) AND a gen2 image. The gen2 image is what tells the instance to be gen2. In particular, it seems to be metadata on the image. For our use case where we create images from VHDs, this is addressed in the FAQS here: https://docs.microsoft.com/en-us/azure/virtual-machines/generation-2#frequently-asked-questions It looks like a managed disk is required. $ az vm list-skus -l centralus --size Standard_DC4s_v3 --query "[].{HyperVGenerations:capabilities[?name=='HyperVGenerations'].value}" [ { "HyperVGenerations": [ "V2" ] } ] if the vm size's HyperVGenerations value is not included "V1", and now we have not support, how about prompt user early ? when select the Gen2 market image RedHat:ocp-worker:ocp-worker-a:4.8.2021122100, with the Standard_DC4s_v3 still prompt : level=fatal msg=failed to fetch Master Machines: failed to load asset "Install Config": compute[0].platform.azure.type: Invalid value: "Standard_DC4s_v3": only disks with HyperVGeneration V1 are supported expected result: install succeed without error with Standard_DC4s_v3 based on the gen2 market image. For 4.10, we expect V2-only instance types to be rejected when entered in the install config. Marketplace images are only supported through editing the manifests. I have updated the KCS article to reflect this: "If you choose to use an instance type which is only Gen2-compatible, the instance type must be specified when editing the manifests--it cannot be specified in the install config." I am setting this back to ON_QA. Please let me know if there are more questions. Note, we are hoping to add Gen2 support in 4.11, which would make all of this more straightforward. (In reply to Patrick Dillon from comment #8) > For 4.10, we expect V2-only instance types to be rejected when entered in > the install config. Marketplace images are only supported through editing > the manifests. I have updated the KCS article to reflect this: "If you > choose to use an instance type which is only Gen2-compatible, the instance > type must be specified when editing the manifests--it cannot be specified in > the install config." > > I am setting this back to ON_QA. Please let me know if there are more > questions. Note, we are hoping to add Gen2 support in 4.11, which would make > all of this more straightforward. Thanks 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 (OpenShift Container Platform 4.10.5 bug fix 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/RHBA-2022:0928 |