cloud-init halts without running include file completely since this morning

[Luis Arias]

This morning cloud-init stopped running the second and third urls in user data using the include file format.

Grepping the cloud-init.log show that the url is accessed and part-002 (and part-003) scripts are created but they never run.

root@ip-10-36-189-88:/var/log/apt# grep part-002 ../cloud-init.log
2013-06-14 08:32:42,712 - __init__.py[DEBUG]: {'Content-Type': 'text/x-shellscript', 'Content-Disposition': 'attachment; filename="part-002"', 'MIME-Version': '1.0'}
2013-06-14 08:32:42,712 - __init__.py[DEBUG]: Calling handler ShellScriptPartHandler: [['text/x-shellscript']] (text/x-shellscript, part-002, 2) with frequency once-per-instance
2013-06-14 08:32:42,712 - util.py[DEBUG]: Writing to /var/lib/cloud/instance/scripts/part-002 - wb: [448] 11580244 bytes

If I set apt_upgrade: false in the cloudconfig.yaml file then things work as before. apt_update: true is set in both the failing and non-failing cases. I'm attaching the apt history.log for an instance that no longer initializes correctly. I have looked through the first set of packages that are installed but don't see any direct dependencies of cloud-init that could affect its behavior.

[Scott Moser (smoser)]

I suspect that this is a dupe of Bug #1124384: Configuration reload clears event that others jobs may be waiting on.
See also bug 1103881.

If you believe otherwise, feel free to un-dupe with a explanation.

Thanks for reporting this bug.