[08:39] <aisrael> I've recently started having issues with cloud-init on an ubuntu-trusty cloud image, on lxd. The cloud-init.log (http://paste.ubuntu.com/23873799/) seems to indicate the error is related to importer.py not being able to import the module 'ubuntu'. Any thoughts on how to fix this?
[08:41] <aisrael> And /usr/lib/python3/dist-packages/cloudinit/ doesn't exist in the image
[08:46] <aisrael> ok, so trusty has cloudinit installed for python2.7
=== shardy_afk is now known as shardy
[09:01] <aisrael> I think that lib is a non-issue. It gets properly imported later. It does seem like cloud-init isn't fully running, though
[09:12] <aisrael> the config and final modules don't seem to be running. I'm running them manually and it's doing what I expect
[09:23] <aisrael> smoser: ^ when you're in
=== shardy is now known as shardy_lunch
=== shardy_lunch is now known as shardy
[14:37] <smoser> aisrael, your log shows cloud-init init-local running
[14:38] <smoser> oh i see. hm.. config and final are not running there.
[14:38] <smoser> sorry, read your ocomment wrong.
[14:46] <smoser> aisrael, possibly you do not have rsyslog ? or its not running ?
[14:51] <smoser> aisrael, fwiw, i just launched a bare container, and it ran fine.
[16:31] <aisrael> smoser, Yeah, it works on another machine for me. Lemme check rsyslog
[16:32] <aisrael> smoser, it's installed. Where cloud-init seems to stop is before starting the ssh service
[16:34] <aisrael> smoser, launching trusty in lxd works as normal. doing a juju add-machine, the container comes up in lxd, gets an ip, but stops after that
[16:37] <smoser> /etc/init/cloud-config.conf
[16:37] <smoser>  start on (filesystem and started rsyslog)
[16:37] <smoser> it seems like you're getting cloud-init's other jobs fine
[16:38] <smoser> so either filesystem or rsyslog would seem to be not getting reached
[16:42] <aisrael> interesting! I'll start debugging from there. thanks, smoser