yahoo-eng-team team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

fixed in 0.7.6

** Changed in: cloud-init
       Status: Fix Committed => Fix Released

-- 
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/1338614

Title:
  Backgrounded resizing does not work

Status in Init scripts for use on cloud images:
  Fix Released

Bug description:
  When setting resize_rootfs to 'noblock', cloud-init should fork a new
  process and continue with it's own initialization process.  However,
  it seems that this is currently broken, as you see from these logs
  that it still blocks on it:

  Jul  7 12:34:20 localhost [CLOUDINIT] cc_resizefs.py[DEBUG]: Resizing (via forking) root filesystem (type=ext4, val=noblock)
  Jul  7 12:34:20 localhost [CLOUDINIT] util.py[WARNING]: Failed forking and calling callback NoneType
  Jul  7 12:34:20 localhost [CLOUDINIT] util.py[DEBUG]: Failed forking and calling callback NoneType#012Traceback (most recent call last):#012  File "/usr/lib/python2.6/site-packages/cloudinit/util.py", line 220, in fork_cb#012    child_cb(*args)#012TypeError: 'NoneType' object is not callable

  Also, when looking at timings, you can see that it was blocked on it
  for the whole time

  Jul  7 12:33:38 localhost [CLOUDINIT] util.py[DEBUG]: Cloud-init v. 0.7.4 running 'init' at Mon, 07 Jul 2014 12:33:38 +0000. Up 5.67 seconds.
  Jul  7 12:34:20 localhost [CLOUDINIT] util.py[DEBUG]: backgrounded Resizing took 41.487 seconds
  Jul  7 12:34:20 localhost [CLOUDINIT] util.py[DEBUG]: cloud-init mode 'init' took 41.799 seconds (41.80)

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