On Fri, Oct 17, 2014 at 08:31:02PM +0200, Juerg Haefliger wrote: > Attached. Let me know if there are questions. I ran pylint against it which > flagged some missing python packages. I installed the resulting package in > a C6 image and did some very limited testing. Basically booting an instance > and verifying that SSH injection works and the centos user is created and > that no funny warnings/errors are spit out. What I noticed though is that > the debug output doesn't go to the cloud-init log, don't know why that is. > I noticed this too (see [1]). What I determined is that the complicated cloud-init logging set up in [2] doesn't default to putting the debug output in that log. As shown by [1], if you are on a systemd based system (EL7,Fedora) you can still get the output. Dusty [1] - http://dustymabe.com/2014/09/08/capture-elusive-cloud-init-debug-output-with-journalctl/ [2] - http://dustymabe.com/content/2014-09-08/05_logging.cfg