baremetal-deploy-helper fails to create partitions
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Arata Notsu |
Bug Description
sfdisk says 'bad input'. The input is, for example, "1 10240 83;\n- 1024 82;\n0 0;\n0 0;\n". If "--force" option is passed to sfdisk, it results in:
Device Boot Start End MiB #blocks Id System
/dev/sdb1 0+ 10244- 10245- 10490444+ 83 Linux
/dev/sdb2 10236+ 11264- 1028- 1052257+ 82 Linux swap / Solaris
/dev/sdb3 0 - 0 0 0 Empty
/dev/sdb4 0 - 0 0 0 Empty
The start of the second partition is set in the first partition. It seems
sfdisk's bug (I tried this in Ubuntu x86_64 12.04 and 12.10).
The following is the log:
2013-04-08 18:37:59 ERROR [nova.virt.
2013-04-08 18:37:59 ERROR [nova.virt.
Disk /dev/disk/
Old situation:
Units = mebibytes of 1048576 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End MiB #blocks Id System
/dev/disk/
/dev/disk/
/dev/disk/
/dev/disk/
2013-04-08 18:37:59 ERROR [nova.virt.
OK
Warning: bad partition start (earliest 10245)
sfdisk: bad input
description: | updated |
description: | updated |
description: | updated |
Changed in nova: | |
milestone: | none → havana-1 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | havana-1 → 2013.2 |
I found that we can avoid the problem using an input such as ",1024,82;" instead of "- 1024 82".