bare metal deploy uses non-scripting mode fdisk, breaks on quantal
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Chris Krelle |
Bug Description
On quantal, fdisk has changed its UI (which it is allowed to as its not a scripting tool).
So we see:
nova-deploy-helper generates: sudo fdisk /dev/disk/
Command (m for help): n Partition type: p primary (0 primary, 0 extended, 4 free) e extended Select (default p): p Partition number (1-4, default 1): 1 First sector (2048-4194303, default 2048): Using default value 2048 Last sector, +sectors or +size{K,M,G} (2048-4194303, default 4194303): +1024M
Command (m for help): t Selected partition 1 Hex code (type L to list codes): 1 Changed system type of partition 1 to 1 (FAT12)
^ generated from the keystrokes 'n,p,1,
A better tool to use is /sbin/sfdisk which has a scripting interface - for instance,
sudo sfdisk $IMAGE_BLOCK_DEVICE << EOF
1 - - *
0 0;
0 0;
0 0;
EOF
Will make a new partition table, allocate everything to the first partition.
Changed in nova: | |
assignee: | nobody → Devananda van der Veen (devananda) |
milestone: | none → havana-1 |
Changed in nova: | |
assignee: | Devananda van der Veen (devananda) → Chris Krelle (nobodycam) |
status: | Triaged → In Progress |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | havana-1 → 2013.2 |
(and sgdisk for GPT tables once we get real big disks ;))