Bug 1954707 - Azure VHD fails to install on gen2 NDv2 instances
Summary: Azure VHD fails to install on gen2 NDv2 instances
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RHCOS
Version: 4.7
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Micah Abbott
QA Contact: Michael Nguyen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-28 16:11 UTC by Jonathan Edwards
Modified: 2021-05-11 23:12 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-11 23:12:01 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github coreos ignition issues 1194 0 None open Support Azure generation 2 VMs 2021-04-29 22:32:31 UTC

Description Jonathan Edwards 2021-04-28 16:11:53 UTC
Instantiating a RHCOS worker node into an existing 4.7 cluster using a Gen 2 Azure NDv2 instance fails complaining that it can't find the ATA virtual CD device:
---
ignition[1120]: failed to open config device: open /dev/disk/by-id/ata-Virtual_CD: no such file or directory
---
it appears that we assume an ATA IDE based CD rom device:
https://github.com/coreos/ignition/blob/master/internal/providers/azure/azure.go#L37-L40

however gen 2 instances on Azure use the virtual scsi devices:
https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/plan/should-i-create-a-generation-1-or-2-virtual-machine-in-hyper-v#what-are-the-advantages-of-using-generation-2-virtual-machines

Comment 4 Benjamin Gilbert 2021-04-29 22:32:35 UTC
Upstream RFE for Ignition support of Gen2 instances: https://github.com/coreos/ignition/issues/1194

Comment 6 Benjamin Gilbert 2021-05-11 23:12:01 UTC
Ignition currently does not support Azure Gen 2 VMs.  An RFE has been filed upstream in https://github.com/coreos/ignition/issues/1194 and we expect to deliver this functionality in a future release.  Thanks for reporting.


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