yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #80607
[Bug 1851438] [NEW] cloud-init disk_setup fails to partition disk for Ubuntu18
Public bug reported:
Pasting disk_setup for cloud-config:
disk_setup:
/dev/xvde:
layout: True
overwrite: False
type: mbr
fs_setup:
-device: /dev/xvde
filesystem: ext4
label: data
overwrite: false
partition: auto
I want to attach and mount a /data disk on the VM using cloud-init so I
just want to single partition 100% of the disk.
Error while running the sfdisk command for partitioning the disk (please see attached file).
OS: Ubuntu18
How I repro-ed it outside cloud-init environment:
1. Open XenCenter, add a new disk, say /dev/xvdc
2. Run `/sbin/sfdisk --Linux --unit=S --force /dev/xvdc` and specify start sector as 0. Because from the cloud-init logs and source code, I figured that it was picking start sector as 0. Save it and see the error.
** Affects: cloud-init
Importance: Undecided
Status: New
** Tags: cloud-init
** Attachment added: "cloud-init-disk-setup-err.PNG"
https://bugs.launchpad.net/bugs/1851438/+attachment/5303120/+files/cloud-init-disk-setup-err.PNG
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1851438
Title:
cloud-init disk_setup fails to partition disk for Ubuntu18
Status in cloud-init:
New
Bug description:
Pasting disk_setup for cloud-config:
disk_setup:
/dev/xvde:
layout: True
overwrite: False
type: mbr
fs_setup:
-device: /dev/xvde
filesystem: ext4
label: data
overwrite: false
partition: auto
I want to attach and mount a /data disk on the VM using cloud-init so
I just want to single partition 100% of the disk.
Error while running the sfdisk command for partitioning the disk (please see attached file).
OS: Ubuntu18
How I repro-ed it outside cloud-init environment:
1. Open XenCenter, add a new disk, say /dev/xvdc
2. Run `/sbin/sfdisk --Linux --unit=S --force /dev/xvdc` and specify start sector as 0. Because from the cloud-init logs and source code, I figured that it was picking start sector as 0. Save it and see the error.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1851438/+subscriptions
Follow ups