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

Bug 1946302

Summary:	Single Node OpenShift installation fails because of disk issue.
Product:	OpenShift Container Platform	Reporter:	Anil Vishnoi <avishnoi>
Component:	assisted-installer	Assignee:	Rom Freiman <rfreiman>
assisted-installer sub component:	Installer	QA Contact:	Udi Kalifon <ukalifon>
Status:	CLOSED CURRENTRELEASE	Docs Contact:
Severity:	medium
Priority:	medium	CC:	aos-bugs, atraeger, ohochman, otuchfel, rfreiman, yobshans
Version:	4.8	Flags:	rfreiman: needinfo+
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:	AI-Team-Core
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-08-28 08:45:59 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 Anil Vishnoi 2021-04-05 18:11:52 UTC

Description of problem:
Single Node OpenShift (SNO) installation through Assisted Installer failed with following error

```
Error
This host failed its installation.
Failed - failed after 3 attempts, last error: failed executing nsenter [-t 1 -m -i -- coreos-installer install --insecure -i /opt/openshift/master.ign /dev/disk/by-id/wwn-0x55cd2e4150c050fa], Error exit status 1, LastOutput "Error: checking for exclusive access to /dev/disk/by-id/wwn-0x55cd2e4150c050fa Caused by: couldn't find /sys/block directory for partition /dev/sda1 of /dev/disk/by-id/wwn-0x55cd2e4150c050fa".
```

When i attempted to reinstall using a different disk partition, installation was successful. 


Version-Release number of selected component (if applicable):
SNO 4.8-alpha

How reproducible:
I attempted only once, but i believe we can reproduce it again if we attempt to install SNO on /dev/sda1 disk again.

Steps to Reproduce:
1. Start SNO installation using Assisted Installation 
2. If default disk is not set to /dev/sda1, set it to /dev/sda1 and continue installation
3. It should fail, while copying the live disk to this partition.

Actual results:
Failed to copy live disk to the partition because of the permission issue. 

Expected results:
Successful SNO installation using /dev/sda1

Additional info:

Comment 1 Ronnie Lazar 2021-04-06 06:17:37 UTC

@atraeger, @rfreiman I don't think we support installing on a partition instead on a disk.
Maybe we should verify this in the API?

Comment 2 Avishay Traeger 2021-04-06 06:27:04 UTC

We are validating that the selected disk is one of those that is in the inventory, so we should already be validating that.  Looks like either a bug in the validation, or the inventory includes partitions as well as full disks (probably the latter).

Comment 3 Michael Levy 2021-04-06 10:49:52 UTC

@avishnoi did you mount the disk manually? do you have any idea why the disk was busy?
just want to verify that it's not related to the machine

Comment 4 Michael Levy 2021-04-06 10:52:25 UTC

do you have logs to share?
thanks

Comment 5 Omer Tuchfeld 2021-04-14 08:01:17 UTC

Got access to the machine, attempted installation on /dev/sda, issue did not reproduce

Comment 6 Omer Tuchfeld 2021-04-14 08:12:43 UTC

Reporter recalls generating an ISO, waiting too long (8 hours or so), attempting an install on /dev/sda, failing due to some error (maybe certificate expiry), then generating a new ISO and trying on /dev/sda again - that's when the bug occurred.

Comment 7 Omri Hochman 2021-05-20 14:26:19 UTC

according to Ronnie, this issue might be already fixed - Anil can you see if it reproduces to you?

Comment 8 Udi Kalifon 2021-06-01 20:05:13 UTC

I tried creating 2 partitions on /dev/sda, but the installer only lets me choose between /dev/sda and /dev/sdb. There is no resolution to partitions.
Verified in v1.5.22 (backend 1.0.22.1)