Hide Forgot
rhts_partitions snippet needs to be modified in order to take in account ondisk option in the kickstart metadata field when doing clearpart. Now it does clearpart --all --initlabel which will destroy data on a hard disk you wish to save specifying ondisk=$other_disk and even worse: the install will fail if you have a multipath device.
(In reply to comment #0) > rhts_partitions snippet needs to be modified in order to take in account ondisk > option in the kickstart metadata field when doing clearpart. > > Now it does clearpart --all --initlabel which will destroy data on a hard disk > you wish to save specifying ondisk=$other_disk and even worse: the install will > fail if you have a multipath device. Will the fix "clearpart --drivers $ondisk --all --initlabel" solve your problem. Did not clear all partitions just clear the target disk.
Yes, this should do it.
Re-open this bug. After production beaker upgrade to 0.8.2, I got regression issue and might be introduced by this bug. Before 0.8.1, I can use this "KickStart MetaData" options: ==== ondisk=/dev/disk/by-id/dm-uuid-mpath-360a98000572d574a4e6f6a5379754f78 ==== But in 0.8.2, I got these error: ===== The following error was found while parsing the kickstart configuration file: The following problem occurred on line 51 of the kickstart file: Specified nonexistent disk /dev/disk/by-id/dm-uuid-mpath-360a98000572d574a4e6f6a5379754f78 in clearpart command install exited abnormally [1/1] The system will be rebooted when you press Ctrl-C or Ctrl-Alt-Delete. ===== Now, only "ondisk=mpatha" can work, but this is NOT a good option for RHEL 6 as its mpath name is keeping changing. This issue impact the WHOLE Storage-QE's testing, please prioritize it. Setting Regression test and rise priority to URGENT. Storage-QE will take QA work. TO workaround this issue, QE need to use this job.xml: ===== <ks_appends> <ks_append><![CDATA[ %end ignoredisk --only-use=disk/by-id/scsi-360a98000572d574a4e6f63706772594b ]]></ks_append> </ks_appends> =====
It might be caused by anaconda "clearpart" option doesn't support "/dev/disk/" path. I will check with their dev. Even this is a bug of anaconda, I suggest we keep the old way.
(In reply to comment #4) > Re-open this bug. > > After production beaker upgrade to 0.8.2, I got regression issue and might be > introduced by this bug. > > Before 0.8.1, I can use this "KickStart MetaData" options: > ==== > ondisk=/dev/disk/by-id/dm-uuid-mpath-360a98000572d574a4e6f6a5379754f78 > ==== > > But in 0.8.2, I got these error: > ===== > The following error was found while parsing the kickstart configuration file: > > The following problem occurred on line 51 of the kickstart file: > > Specified nonexistent disk > /dev/disk/by-id/dm-uuid-mpath-360a98000572d574a4e6f6a5379754f78 in clearpart > command Can you try passing the following: ondisk=disk/by-id/dm-uuid-mpath-360a98000572d574a4e6f6a5379754f78 and please report the job number privately. Thanks!
This option by pass this issue: ondisk=/dev/disk/by-id/scsi-360a98000572d574a4e6f63706772594b You are feel to close this bug or you want this bug for document update. I will work with anaconda team to find a better way or better document for this kickstart option in Bug #817213. Thanks.
closing, issue is with anaconda.