OpenShift SNO on Azure is booting to discovery ISO

Macinga Milan 0

Hi Community,

I have Azure subscription and need to install OpenShift as Single node. I have manage this and the cluster was online and reachable using redhat console, however, after the restart of the cluster on Azure, VM booted again from the discovery ISO and therefore in the cluster events logs I can see logical error:

Failed to register host ........: Host is trying to register after the cluster has already been installed. That most probably means that the host is booting from the installation ISO, and therefore not effectively joining the cluster. The request will be ignored. Fix the boot order and reboot the host.

The VM was created from the converted discovery ISO to vhd and in Azure I can see the ISO disk as the OS disk and the sda (see table below) as the additional attached disk. I cannot see the sdb as the bootable installation.

The size of the VM is Standard D16s v3 (16 vcpus, 64 GiB memory).

I am strugling how to proceed and how to change the Boot order in Azure to boot from the installed OpenShift instead of ISO. The disk configuration from RedHat cluster dashboard looks as follwed:

3 Disk

Name	Role	Limitations	Drive type	Size	Model
sda	None		HDD	1.10 TB	Virtual_Disk
sda	None		HDD	1.10 TB	Virtual_Disk
sdb (bootable)	Installation disk		HDD	137.44 GB	Virtual_Disk
sdc (bootable)	None	1	HDD	1.10 TB

sdc is the installation ISO.

Could you please point me how to proceed with the discovery ISO removal?

I have tryied to swap the OS disk, but since I cannot see the installation, I cannot use the sdb. In addition, I cannot logon to the OpenShift while the Identities were not set yet and I was trying to move further via Azure, CLI/PS without success.

Thank you very much.

Akshay kumar Mandha 1,655 Reputation points Microsoft Vendor

2024-11-22T01:34:35.6833333+00:00

Hi Macinga Milan,
Welcome to the Microsoft Q&A and thank you for posting your questions here.
We are reviewing your query openShift SNO on azure is booting to discovery ISO we will update you shortly
Akshay kumar Mandha 1,655 Reputation points Microsoft Vendor

2024-11-22T12:22:46.2133333+00:00

Hi Macinga Milan,
Thank you for your patience while review your query.
I understand your concern regarding disk you are able to see the ISO disk sdc and the sda, but you are unable to see the sdb OS disk. Could you please share the documentation you are following for this setup? Providing this information will help us suggest a solution and resolve the issue quickly
Macinga Milan 0 Reputation points

2024-11-22T13:09:59.8266667+00:00
Hello,

since there is no comprehesive documentation how to install SNO instance of OpenShift on Azure I have proceeded as followed:

Download the discovery ISO for SNO installation from RedHat

Convert the ISO to VHD using quemu https://superuser.com/questions/1486564/convert-iso-image-to-vhd

Convert the VHD to Fixed using PowerShell convert-VHD -Path "PathToVHD\OpenShift-MAS.vhd" -DestinationPath "DestinationPath\OpenShift-MAS-sandbox-fx.vhd" -VHDType Fixed

Resize the vhd to exact MB size using Resize-VHD -Path "PathToVHDfromStep3\OpenShift-MAS--fx.vhd" -SizeBytes 1174MB

Upload the converted disk to StorageBlob as PageBlob

Create new Linux OS Type managed disk / Standard / Gen2 / x64 from uploaded VHD in StorageBlob under the ResourceGroup

Create VM from Storage Blob VHD

Select the VM template with local disk (d16s v3) 16vcpus, 64G RAM)

Attach additional empty data disk

Start the VM

Check the cluster on RedHat Hybrid Console

Add the routes in DNS to accept the communication to master domain

Connect to the openshift-console-domain

Above listed worked without any problem. The issue started when I want to logon to the os VM, which was not possible, keys were not accepted, access denied and after the restart of the VM, the cluster hang in "Stale" state, while VM booted from installation VHD converted from RedHat discovery.iso.

The main topic is to install SingleNodeOperation OpenShift on Azure.
Akshay kumar Mandha 1,655 Reputation points Microsoft Vendor

2024-11-25T11:05:56.41+00:00

Hi Macinga Milan,
As you mentioned latest, you are getting an 'Access Denied' error while logging into the VM. Could you please provide the full error message screenshot or copy the error text and post here it would help us better understand the issue and resolve it more quickly
Thank you.!
Akshay kumar Mandha 1,655 Reputation points Microsoft Vendor

2024-11-26T06:55:26.5333333+00:00

Hi Macinga Milan,
Could you please review the latest comment on this post and let us know
Thank you.!
Macinga Milan 0 Reputation points

2024-11-26T06:57:41.85+00:00

Hello,

access denied was meanwhile solved. Hence the changing ISO.vhd to installation disk is still the topic.
Akshay kumar Mandha 1,655 Reputation points Microsoft Vendor

2024-11-26T14:52:28.39+00:00

Hi Macinga Milan,
Got it, let's revise things for better understanding. When creating the VM, by default, it will use the sda disk. You have attached the sdb disk to store the OpenShift installation, and sdc is the converted VHD. It seems you are trying to swap the OS, but as mentioned in your original query, you're not able to see the sdb disk.

The sdb disk is the additional disk, and the question is whether it is currently visible in the Azure portal. In the VM's disk section, can you confirm if the three disks (sda, sdb, and sdc) are showing? If sdb is visible in the VM's disk section, you can swap the OS by setting sdc as the primary disk. After starting the VM, the boot process should begin from sdc. Once booted, you can then set sdb as the primary disk.

Based on your query, this scenario should work. Have you tried this process? Please let us know if I have understood the situation correctly. If not, kindly provide more details, and we’ll be happy to help you resolve the issue

Please let us know after trying above process and tag us in comment
Macinga Milan 0 Reputation points

2024-11-26T15:01:35.3866667+00:00

Hello,

the sdb disk is not visible in the VM disk section, only in RedHat portal under Cluster specs. That is why I cannot swap between the ISO.vhd and the OS installation disk.
Akshay kumar Mandha 1,655 Reputation points Microsoft Vendor

2024-11-27T07:45:54.27+00:00

Hi Macinga Milan,
We understand your point. you have created and managed the sdb disk from a VHD, correct? It was not taken as a separate additional disk from the Azure portal instead, it was managed from the VHD. If that's the case could you confirm how you created the managed disk when attaching the VHD? Was it manually attached sdb in the disk section, or does it get attached automatically when you attach the VHD disk?Please let me know if I have understood the situation correctly. Also, check sometimes the VM's deployed region, and the Blob Storage region should be the same region.

Please check the resource are in the same region Let us know how it goes after trying the process, and feel free to tag us in the comment.
Macinga Milan 0 Reputation points

2024-11-27T07:56:23.92+00:00

Hello,

the disk was created automatically by VM. Only Mounted installation vhd(ISO) and the sdc disk for data were manually created. Regions are for all resources the same. germanywestcentral
Akshay kumar Mandha 1,655 Reputation points Microsoft Vendor

2024-11-27T08:27:19.34+00:00

Hi Macinga Milan,
By default, the OS disk will be labeled as sda for the VM. How did you attach the sdc VHD disk to the VM? How did you create the sdb disk from the VHD? If you created the sdb disk from the VHD, can you explain how the sdb disk was created and attached? If we get more clarity, we can identify the issue and sort it out based on the information provided
Akshay kumar Mandha 1,655 Reputation points Microsoft Vendor

2024-11-28T12:47:15.51+00:00

Hi Macinga Milan,
Any updates on this latest comment.! Any progress you have made in the meantime please let us know
Macinga Milan 0 Reputation points

2024-11-28T13:28:53.24+00:00

During the creation of VM I have created Storage Blob, where I have uploaded converted ISO to VHD. Then I have Created disk and attached VHD from the storage blob. Then, I go to the disk with the ISO(VHD) and click on create VM, then go through the process and under disks I have attached another Data disk for this VM. The type of the VM was d16s v3 with the disk within the type.
Akshay kumar Mandha 1,655 Reputation points Microsoft Vendor

2024-11-29T09:46:59.54+00:00

Hi Macinga Milan,
We are looking into the query and will update you ASAP, until that time, if you make any progress, please share it with us.
Thank you
Akshay kumar Mandha 1,655 Reputation points Microsoft Vendor

2024-12-13T18:03:40.3+00:00

Hi Macinga Milan,
I hope you are doing well.
We recommend raising a support ticket for this issue, as it is visible on the OpenShift console but not visible from the Azure portal. There may be an issue with the portal. Please raise a support request and explain the situation regarding the environment.
Please refer to the documentation below for the support request
Create an Azure support request
Thank you.!

Share via

OpenShift SNO on Azure is booting to discovery ISO

Your answer