Sorry, I forgot all about this bug report. We fixed the problem long
ago....
IIRC it turned out not to be a cloud-init problem, cloud-init just
changed the timing. We initially fixed it by patching a cloud-init
script, but even that patch was later removed. So cloud-init is
completely exonerated!
** Changed in: cloud-init
Status: Incomplete => Invalid
--
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/1326140
Title:
Cannot repartition root
Status in Init scripts for use on cloud images:
Invalid
Bug description:
I need to repartition the root drive. After repartitioning everything
looks good. e2fsck -f /etc/sda1 works and I can make a file system and
mount the new partition.
However, when I reboot it fails with: bad geometry: block count
exceeds size of device. However, the exact same code works if I first
apt-get purge cloud-init.
I am testing in hyper-v with a Ubuntu 14.04 image downloaded from
Azure.
The same code also works in vmware and a modified version works in
centos.
I don't understand how cloud-init could be affecting things since it
fails well before cloud-init starts.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1326140/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
