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.
@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
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
@sasha it's definitely not a bug but an RFE. Can we close this ticket? See the above comments
Confirm that the cleaning step isn't needed anymore.