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

[Scott Moser]

I dont think i follow what you meant by "parse the output for the
warning and answer yes".

Example:
$ echo "1,1000,L" | sudo sfdisk /dev/vdb
$ grep "vdb" /proc/partitions 
 253       16   20971520 vdb
 253       17     504000 vdb1
$ sudo mkfs /dev/vdb1
$ sudo mount /dev/vdb1 /mnt

## now /dev/vdb is busy (mounted) try to resizepart on it.

$ sudo parted /dev/vdb resizepart 1 </dev/null
Warning: Partition /dev/vdb1 is being used. Are you sure you want to continue?
$ echo $?
1

# so that didn't resize (reading from /dev/null).  Not surprising. 
# try with 'Yes' to stdin.
echo "Yes" | sudo parted /dev/vdb resizepart 1; echo $?
Warning: Partition /dev/vdb1 is being used. Are you sure you want to continue?
1

I also failed in an attempt with 'expect', but not sure thats relevant
as I dont want to use expect anyway, and I might have done something
wrong.

-- 
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:
  Confirmed
Status in “cloud-init” package in Ubuntu:
  Confirmed
Status in “parted” package in Ubuntu:
  New

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