[Bug 1212492] Re: cc_growpart broken if parted resizefs found

[Scott Moser]

Ok.
  I'm not even sure if resizepart can be made to work, at all.


$ parted --help | grep resizepart
  resizepart NUMBER END                    resize partition NUMBER

the END seems to be in MB, which is insufficient for my needs.  I'd like it to grow it to the next partition.
There isn't a way to just say "make it as big as possible".

The undocumented flag for --script is '---pretend-input-tty', but I
can't even seem to make that work.

It just seems to ignore things like this:

$ echo "Yes" | sudo parted ---pretend-input-tty /dev/vdb resizepart  1 1000 --machine --script 
Warning: Shrinking a partition can cause data loss, are you sure you want to continue?
$ echo $?
0

but it doesn't shrink the partition table

I'm going to remove the support for parted from cloud-init entirely.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to parted in Ubuntu.
https://bugs.launchpad.net/bugs/1212492

Title:
  cc_growpart broken if parted resizefs found

Status in Init scripts for use on cloud images:
  Won't Fix
Status in “cloud-init” package in Ubuntu:
  Won't Fix

Bug description:
  As reported in bug 1212444, the partition growing is broken if growpart is found to be usable.
  There are 2 things that are broken,
   a.) we invoke parted wrong (passing device after 'resizepart' rather than before)
   b.) parted seems somewhat broken, and I dont know how to force it to do what we want.  See:

  $ sudo parted /dev/vda resizepart  --script 1 </dev/null; echo $?
  Warning: Partition /dev/vda1 is being used. Are you sure you want to continue?
  1

  Um... yes, parted, i want you to do what I told you to do.

  Related bugs:
   * bug 1212444: cc_growpart failed in auto grow mode with "Error: Could not stat device resizepart - No such file or directory." with parted 2.3-14

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1212492/+subscriptions