[Bug 1460715] Re: MBR disk setup fails because sfdisk no longer accepts M as a valid unit
This bug was fixed in the package cloud-init - 0.7.8-68-gca3ae67-0ubuntu1~16.10.1 --- cloud-init (0.7.8-68-gca3ae67-0ubuntu1~16.10.1) yakkety; urgency=medium * debian/cherry-pick: add utility for cherry picking commits from upstream into patches in debian/patches. * New upstream snapshot. - mounts: use mount -a again to accomplish mounts (LP: #1647708) - CloudSigma: Fix bug where datasource was not loaded in local search. (LP: #1648380) - when adding a user, strip whitespace from group list [Lars Kellogg-Stedman] (LP: #1354694) - fix decoding of utf-8 chars in yaml test - Replace usage of sys_netdev_info with read_sys_net (LP: #1625766) - fix problems found in python2.6 test. - OpenStack: extend physical types to include hyperv, hw_veb, vhost_user. (LP: #1642679) - tests: fix assumptions that expected no eth0 in system. (LP: #1644043) - net/cmdline: Consider ip= or ip6= on command line not only ip= (LP: #1639930) - Just use file logging by default [Joshua Harlow] (LP: #1643990) - Improve formatting for ProcessExecutionError [Wesley Wiedenmeier] - flake8: fix trailing white space - Doc: various documentation fixes [Sean Bright] - cloudinit/config/cc_rh_subscription.py: Remove repos before adding [Brent Baude] - packages/redhat: fix rpm spec file. - main: set TZ in environment if not already set. [Ryan Harper] - disk_setup: Use sectors as unit when formatting MBR disks with sfdisk. [Daniel Watkins] (LP: #1460715) -- Scott MoserMon, 19 Dec 2016 15:07:12 -0500 ** Changed in: cloud-init (Ubuntu Yakkety) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460715 Title: MBR disk setup fails because sfdisk no longer accepts M as a valid unit To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1460715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460715] Re: MBR disk setup fails because sfdisk no longer accepts M as a valid unit
Marking this verification-done for yakkety. ## fresh instance openstack kvm instance of yakkety. $ dpkg-query --show cloud-init cloud-init 0.7.8-49-g9e904bb-0ubuntu1~16.10.1 $ lsb_release -sc yakkety $ cat /etc/cloud/build.info build_name: server serial: 20170114 $ m=http://archive.ubuntu.com/ubuntu $ echo deb $m $(lsb_release -sc)-proposed main | sudo tee /etc/apt/sources.list.d/proposed.list $ sudo apt-get -qy update && sudo apt-get -qy install cloud-init https://bugs.launchpad.net/bugs/1460715 Title: MBR disk setup fails because sfdisk no longer accepts M as a valid unit To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1460715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460715] Re: MBR disk setup fails because sfdisk no longer accepts M as a valid unit
Hello Dan, or anyone else affected, Accepted cloud-init into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud- init/0.7.8-68-gca3ae67-0ubuntu1~16.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-init (Ubuntu Yakkety) Status: In Progress => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460715 Title: MBR disk setup fails because sfdisk no longer accepts M as a valid unit To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1460715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460715] Re: MBR disk setup fails because sfdisk no longer accepts M as a valid unit
This is fixed in cloud-init 0.7.9. ** Changed in: cloud-init Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460715 Title: MBR disk setup fails because sfdisk no longer accepts M as a valid unit To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1460715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460715] Re: MBR disk setup fails because sfdisk no longer accepts M as a valid unit
This bug was fixed in the package cloud-init - 0.7.8-49-g9e904bb- 0ubuntu1~16.04.2 --- cloud-init (0.7.8-49-g9e904bb-0ubuntu1~16.04.2) xenial-proposed; urgency=medium * cherry-pick 18203bf: disk_setup: Use sectors as unit when formatting MBR disks with sfdisk. (LP: #1460715) * cherry-pick 6e92c5f: net/cmdline: Consider ip= or ip6= on command line not only ip= (LP: #1639930) * cherry-pick 8c6878a: tests: fix assumptions that expected no eth0 in system. (LP: #1644043) * cherry-pick 2d2ec70: OpenStack: extend physical types to include hyperv, hw_veb, vhost_user. (LP: #1642679) -- Scott MoserThu, 01 Dec 2016 16:57:39 -0500 ** Changed in: cloud-init (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460715 Title: MBR disk setup fails because sfdisk no longer accepts M as a valid unit To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1460715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460715] Re: MBR disk setup fails because sfdisk no longer accepts M as a valid unit
We don't use the -u option to sfdisk. ** Changed in: ubuntu-image Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460715 Title: MBR disk setup fails because sfdisk no longer accepts M as a valid unit To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1460715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460715] Re: MBR disk setup fails because sfdisk no longer accepts M as a valid unit
heres the same basic thing on azure. $ df Filesystem 1K-blocksUsed Available Use% Mounted on udev 321736 0321736 0% /dev tmpfs 683283216 65112 5% /run /dev/sda1 29711408 1416484 28278540 5% / tmpfs 341636 0341636 0% /dev/shm tmpfs 5120 0 5120 0% /run/lock tmpfs 341636 0341636 0% /sys/fs/cgroup tmpfs 68328 0 68328 0% /run/user/1000 $ dpkg-query --show cloud-init cloud-init 0.7.8-49-g9e904bb-0ubuntu1~16.04.2 $ cat /etc/cloud/build.info build_name: server serial: 20161213 $ df Filesystem 1K-blocksUsed Available Use% Mounted on udev 321736 0321736 0% /dev tmpfs 683283216 65112 5% /run /dev/sda1 29711408 1416484 28278540 5% / tmpfs 341636 0341636 0% /dev/shm tmpfs 5120 0 5120 0% /run/lock tmpfs 341636 0341636 0% /sys/fs/cgroup tmpfs 68328 0 68328 0% /run/user/1000 $ grep [sv]db /proc/partitions 8 16 20971520 sdb 8 17 13841203 sdb1 8 187129088 sdb2 $ cat /etc/fstab # CLOUD_IMG: This file was created/modified by the Cloud Image build process UUID=c50d1651-3fd4-4fae-9d8d-1713e9bb191e /ext4 defaults,discard0 0 /dev/disk/cloud/azure_resource-part1/mnt2 auto defaults,nofail,x-systemd.requires=cloud-init.service,comment=cloudconfig 0 2 /dev/disk/cloud/azure_resource-part2noneswapsw,comment=cloudconfig 00 $ sudo mount -a $ df -h /mnt2 Filesystem Size Used Avail Use% Mounted on /dev/sdb113G 33M 13G 1% /mnt2 $ free totalusedfree shared buff/cache available Mem: 683276 109488 4109203244 162868 445812 Swap: 7129084 0 7129084 $ grep [vs]db2 /proc/swaps /dev/sdb2 partition 7129084 0 -1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460715 Title: MBR disk setup fails because sfdisk no longer accepts M as a valid unit To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1460715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460715] Re: MBR disk setup fails because sfdisk no longer accepts M as a valid unit
This probably affects u-i too. ** Also affects: ubuntu-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460715 Title: MBR disk setup fails because sfdisk no longer accepts M as a valid unit To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1460715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460715] Re: MBR disk setup fails because sfdisk no longer accepts M as a valid unit
The above is verification done on an openstack instance after the 'clean' and reboot as seen in the bug description. ** Description changed: === Begin SRU Template === [Impact] Cloud-init has function to partition disks on devices. Creating partitions on a disk no longer works with sfdisk as recent versions of sfdisk no accept the unit 'M' as input, this function is broken. [Test Case] 1. Launch an instance with provided user-data On Azure, this will work: #cloud-config disk_setup: ephemeral0: table_type: mbr layout: [66, [33, 82]] overwrite: True fs_setup: - device: ephemeral0.1 filesystem: ext4 - device: ephemeral0.2 filesystem: swap mounts: - ["ephemeral0.1", "/mnt2"] - ["ephemeral0.2", "none", "swap", "sw", "0", "0"] On a typical kvm openstack use: #cloud-config disk_setup: /dev/vdb: table_type: mbr layout: [66, [33, 82]] overwrite: True fs_setup: - device: /dev/vdb1 filesystem: ext4 - device: /dev/vdb2 filesystem: swap mounts: - ["/dev/vdb1", "/mnt2"] - ["/dev/vdb2", "none", "swap", "sw", "0", "0"] 2. Add proposed, update, and reboot as fresh instance. # enable proposed echo deb http://archive.ubuntu.com/ubuntu $(lsb_release -sc)-proposed main | sudo tee /etc/apt/sources.list.d/proposed.list -sudo apt-get -qy update && sudo apt-get -qy install cloud-init https://bugs.launchpad.net/bugs/1460715 Title: MBR disk setup fails because sfdisk no longer accepts M as a valid unit To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1460715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460715] Re: MBR disk setup fails because sfdisk no longer accepts M as a valid unit
$ dpkg-query --show cloud-init cloud-init 0.7.8-49-g9e904bb-0ubuntu1~16.04.2 $ cat /etc/cloud/build.info build_name: server serial: 20161214 $ df Filesystem 1K-blocks Used Available Use% Mounted on udev 1018216 0 1018216 0% /dev tmpfs 204836 3180201656 2% /run /dev/vda1 20263528 973360 19273784 5% / tmpfs1024172 0 1024172 0% /dev/shm tmpfs 5120 0 5120 0% /run/lock tmpfs1024172 0 1024172 0% /sys/fs/cgroup tmpfs 204836 0204836 0% /run/user/1000 $ grep [sv]db /proc/partitions 253 16 41943040 vdb 253 17 27682406 vdb1 253 18 14259200 vdb2 $ cat /etc/fstab LABEL=cloudimg-rootfs /ext4 defaults0 0 /dev/vdb1 /mnt2 auto defaults,nofail,x-systemd.requires=cloud-init.service,comment=cloudconfig 0 2 /dev/vdb2 noneswapsw,comment=cloudconfig 0 0 $ sudo mount -a $ df -h /mnt2 Filesystem Size Used Avail Use% Mounted on /dev/vdb126G 44M 25G 1% /mnt2 $ free totalusedfree shared buff/cache available Mem:2048348 48596 18576523208 142100 1844252 Swap: 14259196 014259196 $ grep [vs]db2 /proc/swaps /dev/vdb2 partition 142591960 -1 ** Description changed: === Begin SRU Template === - [Impact] + [Impact] Cloud-init has function to partition disks on devices. Creating partitions on a disk no longer works with sfdisk as recent versions of sfdisk no accept the unit 'M' as input, this function is broken. [Test Case] 1. Launch an instance with provided user-data -On Azure, this will work: - #cloud-config - disk_setup: -ephemeral0: -table_type: mbr -layout: [66, [33, 82]] -overwrite: True - fs_setup: -- device: ephemeral0.1 - filesystem: ext4 -- device: ephemeral0.2 - filesystem: swap - mounts: -- ["ephemeral0.1", "/mnt2"] -- ["ephemeral0.2", "none", "swap", "sw", "0", "0"] + On Azure, this will work: + #cloud-config + disk_setup: + ephemeral0: + table_type: mbr + layout: [66, [33, 82]] + overwrite: True + fs_setup: + - device: ephemeral0.1 + filesystem: ext4 + - device: ephemeral0.2 + filesystem: swap + mounts: + - ["ephemeral0.1", "/mnt2"] + - ["ephemeral0.2", "none", "swap", "sw", "0", "0"] -On a typical kvm openstack use: - #cloud-config - disk_setup: -/dev/vdb: -table_type: mbr -layout: [66, [33, 82]] -overwrite: True - fs_setup: -- device: /dev/vdb1 - filesystem: ext4 -- device: /dev/vdb2 - filesystem: swap - mounts: -- ["/dev/vdb1", "/mnt2"] -- ["/dev/vdb2", "none", "swap", "sw", "0", "0"] + On a typical kvm openstack use: + #cloud-config + disk_setup: + /dev/vdb: + table_type: mbr + layout: [66, [33, 82]] + overwrite: True + fs_setup: + - device: /dev/vdb1 + filesystem: ext4 + - device: /dev/vdb2 + filesystem: swap + mounts: + - ["/dev/vdb1", "/mnt2"] + - ["/dev/vdb2", "none", "swap", "sw", "0", "0"] 2. Add proposed, update, and reboot as fresh instance. -# enable proposed -sudo apt-get -qy update && sudo apt-get -qy install cloud-init -sudo rm -Rf /var/lib/cloud /var/log/cloud-init* -sudo sed -i '/cloudconfig/d' /etc/fstab -sudo reboot + # enable proposed +echo deb http://archive.ubuntu.com/ubuntu $(lsb_release -sc)-proposed main | sudo tee /etc/apt/sources.list.d/proposed.list + sudo apt-get -qy update && sudo apt-get -qy install cloud-init + sudo rm -Rf /var/lib/cloud /var/log/cloud-init* + sudo sed -i '/cloudconfig/d' /etc/fstab + sudo reboot 3. login to system and look around. -The target disk should be partitioned with 2 partitions. + The target disk should be partitioned with 2 partitions. -$ grep [sv]db /proc/partitions -253 16 41943040 vdb -253 17 27682406 vdb1 -253 18 14259200 vdb2 + $ grep [sv]db /proc/partitions + 253 16 41943040 vdb + 253 17 27682406 vdb1 + 253 18 14259200 vdb2 -There should entries in /etc/fstab for the configured devices -$ cat /etc/fstab -LABEL=cloudimg-rootfs / ext4 defaults 0 0 -LABEL=UEFI /boot/efi vfat defaults 0 0 -/dev/vdb1 /mnt2 auto defaults,nofail,x-systemd.requires=cloud-init.service,comment=cloudconfig 0 2 -/dev/vdb2 none swap sw,comment=cloudconfig 0 0 + There should entries in /etc/fstab for the configured devices +
[Bug 1460715] Re: MBR disk setup fails because sfdisk no longer accepts M as a valid unit
Hello Dan, or anyone else affected, Accepted cloud-init into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud-init/0.7.8-49 -g9e904bb-0ubuntu1~16.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-init (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460715 Title: MBR disk setup fails because sfdisk no longer accepts M as a valid unit To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1460715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460715] Re: MBR disk setup fails because sfdisk no longer accepts M as a valid unit
** Changed in: cloud-init (Ubuntu Yakkety) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460715 Title: MBR disk setup fails because sfdisk no longer accepts M as a valid unit To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1460715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460715] Re: MBR disk setup fails because sfdisk no longer accepts M as a valid unit
** Description changed: + === Begin SRU Template === + [Impact] + Cloud-init has function to partition disks on devices. + Creating partitions on a disk no longer works with sfdisk as recent versions of + sfdisk no accept the unit 'M' as input, this function is broken. + + [Test Case] + 1. Launch an instance with provided user-data + +On Azure, this will work: + #cloud-config + disk_setup: +ephemeral0: +table_type: mbr +layout: [66, [33, 82]] +overwrite: True + fs_setup: +- device: ephemeral0.1 + filesystem: ext4 +- device: ephemeral0.2 + filesystem: swap + mounts: +- ["ephemeral0.1", "/mnt2"] +- ["ephemeral0.2", "none", "swap", "sw", "0", "0"] + +On a typical kvm openstack use: + #cloud-config + disk_setup: +/dev/vdb: +table_type: mbr +layout: [66, [33, 82]] +overwrite: True + fs_setup: +- device: /dev/vdb1 + filesystem: ext4 +- device: /dev/vdb2 + filesystem: swap + mounts: +- ["/dev/vdb1", "/mnt2"] +- ["/dev/vdb2", "none", "swap", "sw", "0", "0"] + + 2. Add proposed, update, and reboot as fresh instance. + +# enable proposed +sudo apt-get -qy update && sudo apt-get -qy install cloud-init +sudo rm -Rf /var/lib/cloud /var/log/cloud-init* +sudo sed -i '/cloudconfig/d' /etc/fstab +sudo reboot + + 3. login to system and look around. + +The target disk should be partitioned with 2 partitions. + +$ grep [sv]db /proc/partitions +253 16 41943040 vdb +253 17 27682406 vdb1 +253 18 14259200 vdb2 + +There should entries in /etc/fstab for the configured devices +$ cat /etc/fstab +LABEL=cloudimg-rootfs / ext4 defaults 0 0 +LABEL=UEFI /boot/efi vfat defaults 0 0 +/dev/vdb1 /mnt2 auto defaults,nofail,x-systemd.requires=cloud-init.service,comment=cloudconfig 0 2 +/dev/vdb2 none swap sw,comment=cloudconfig 0 0 + +A 'mount -a' will mount the necessary devices. +Note, these should ideally be already mounted, but an as-yet unidentified +issue (to be fixed in bug 1642383) means they are not mounted on first +boot. +$ mount -a +$ df -h /mnt2 +Filesystem Size Used Avail Use% Mounted on +/dev/vdb126G 45M 25G 1% /mnt2 + +There should be swap used. +$ free + total used free shared buff/cache available +Mem:2047792 73984 1804508 3252 169300 1825896 +Swap: 14259196 014259196 + +$ grep [vs]db2 /proc/swaps +/dev/vdb2 partition 14259196 0 -1 + + + [Regression Potential] + Change from using Megabytes to Sectors could have caused math errors, + most likely with sector sizes other than 512. + Partitioning with sfdisk was broken previously, so it wont be worse. + + === End SRU Template === + Specifically, we get the following output in cc_disk_setup.exec_mkpart_mbr: sfdisk: --Linux option is unnecessary and deprecated sfdisk: unsupported unit 'M' and the manpage says: -u, --unit S Deprecated option. Only the sector unit is supported. So we'll need to shift to using sectors. Related bugs: - * bug 1642383: Unable to configure swap space on ephemeral disk in Azure + * bug 1642383: Unable to configure swap space on ephemeral disk in Azure -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460715 Title: MBR disk setup fails because sfdisk no longer accepts M as a valid unit To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1460715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460715] Re: MBR disk setup fails because sfdisk no longer accepts M as a valid unit
** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu) Status: New => Fix Released ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium ** Also affects: cloud-init (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu Xenial) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu Yakkety) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu Yakkety) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu Xenial) Status: Confirmed => In Progress ** Changed in: cloud-init (Ubuntu Xenial) Assignee: (unassigned) => Scott Moser (smoser) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460715 Title: MBR disk setup fails because sfdisk no longer accepts M as a valid unit To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1460715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs