I've generated a FreeBSD qcow2 including base and kernel with cloud-init and dependencies. cloud-init runs when the instance boots, but the growpart module fails due to, what appears to be, two separate problems.
One of the dependencies is the gpart port/pkg which, incidentally, is a reason it is failing[1]. The growpart module, for a yet unknown reason, is calling /usr/local/sbin/gpart with arguments that are valid only with FreeBSD's /sbin/gpart. cloud-init executes /sbin/gpart when the dependent /usr/local/sbin/gpart is removed that subsequently results in the next failure which I think is caused by cloud-init itself...
cloud-init executes growfs, via resizefs, after successful execution of gpart recover/resize. The logs[2] illustrate the growfs command as growfs /dev/vtbd0p2. By default, FreeBSD's growfs runs interactively asking a question which can be mitigated using the '-y' command line option. The logs indicate a successful growfs operation, but df doesn't reflect it. I suspect the this is due to the default interactive nature of growfs.
[1] http://hostileadmin.com/images/cloud_init_gpart_fail.jpg
[2] http://hostileadmin.com/images/cloud_init_growfs_fail.jpg
Interested to see this from gpart:
2015-01-11 18:49:23,742 - util.py[DEBUG]: Failed: gpart recover /dev/vtbd0
Traceback (most recent call last):
File "/usr/local/
util.
File "/usr/local/
cmd=args)
ProcessExecutio
Command: ['gpart', 'recover', '/dev/vtbd0']
Exit code: 1
Reason: -
Stdout: ''
Stderr: 'Usage: gpart [options] device\nOptions: [-b <backup MBR>][-C c,h,s][
This was stderr:
Usage: gpart [options] device
Options: [-b <backup MBR>][-C c,h,s][
[-K <last sector>][-k <# of sectors>][-L][-l <log file>]
[-n <increment>][-q][-s <sector-size>][-t <module-name>]
gpart v0.1h (c) 1999-2001 Michail Brzitwa <email address hidden>.
Guess PC-type hard disk partitions.
A little rude, but lets see what happens, since the above is most certainly nothing compared with man gpart...
# find / -name gpart
/rescue/gpart
/usr/local/
/sbin/gpart
Bingo: we have gpart in base -and- from ports, and according the initscript cloudinit will use /usr/local/sbin first.
Workaround:
After installing the cloudinit port remove gpart: pkg delete -f gpart
Fix:
Lets remove that port from the required dependencies. Ill see what's required to get that going, I think this only involves pushing out a new port release.
The other issue seems to be with growfs, which doesn't grow the filesystem. The cc_resizefs module should be looking like this:
def _resize_
return ('growfs', '-y', devpth)
After this it'll resize as planned. (I can't believe I missed that -y though...)