Bug 1913975

Summary:	SNO: harddrive needs to be cleaned prior deploying
Product:	OpenShift Container Platform	Reporter:	Alexander Chuzhoy <sasha>
Component:	Documentation	Assignee:	John Wilkins <jowilkin>
Status:	CLOSED NOTABUG	QA Contact:	Xiaoli Tian <xtian>
Severity:	high	Docs Contact:	Tomas 'Sheldon' Radej <tradej>
Priority:	unspecified
Version:	4.8	CC:	aos-bugs, bleanhar, jokerman, kboumedh, mstaeble, pablo.iranzo, yhe
Target Milestone:	---	Keywords:	UpcomingSprint
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	SingleNode
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-08-31 15:12:38 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 Alexander Chuzhoy 2021-01-07 21:53:13 UTC

Version:

SNO 4.7.0-fc.0

Deploying on a disk with existing partitions fails. The following can be seen in logs during the bootstrap phase:


Jan 07 18:55:35 openshift-worker-2.qe3.kni.lab.eng.bos.redhat.com bootkube.sh[3540]: Installing Red Hat Enterprise Linux CoreOS 46.82.202009222340-0 (Ootpa) x86_64 (512-byte sectors)
Jan 07 18:55:37 openshift-worker-2.qe3.kni.lab.eng.bos.redhat.com bootkube.sh[3540]: Partitions in use on /dev/sda:
Jan 07 18:55:37 openshift-worker-2.qe3.kni.lab.eng.bos.redhat.com bootkube.sh[3540]:     /dev/sda2 in use by /dev/dm-1
Jan 07 18:55:37 openshift-worker-2.qe3.kni.lab.eng.bos.redhat.com bootkube.sh[3540]:     /dev/sda2 in use by /dev/dm-2
Jan 07 18:55:37 openshift-worker-2.qe3.kni.lab.eng.bos.redhat.com bootkube.sh[3540]: Error: checking for exclusive access to /dev/sda
Jan 07 18:55:37 openshift-worker-2.qe3.kni.lab.eng.bos.redhat.com bootkube.sh[3540]: Caused by: found busy partitions


Workaround:
Manually remove all existing parititions.

Comment 1 Rom Freiman 2021-01-18 07:25:50 UTC

@sasha it's definitely not a bug but an RFE.

@kboumedh what is usually the guideline regarding partitions cleanup in UPI installation? I cannot find anything in the docs

https://docs.openshift.com/container-platform/4.6/installing/installing_bare_metal/installing-bare-metal.html

Comment 2 Pablo Iranzo Gómez 2021-01-19 11:48:53 UTC

For baremetal, Ironic should take care of cleaning the disk on server usage or when retiring a server and returning it to the pool of available machines.

Step 6.8 at https://openshift-kni.github.io/baremetal-deploy/4.6/Troubleshooting.html#ipi-install-troubleshooting-ironic-bootstrap_ipi-install-troubleshooting

Comment 3 Rom Freiman 2021-01-27 12:18:18 UTC

@sasha it's definitely not a bug but an RFE.
Can we close this ticket? See the above comments

Comment 8 Alexander Chuzhoy 2021-11-15 19:30:49 UTC

Confirm that the cleaning step isn't needed anymore.