[10:30] <CatKiller> Hi there! I've got a small issue with cloud-init on Ubuntu 14.04 desktop edition
[10:30] <CatKiller> I've successfully installed it, but it seems that "dpkg-reconfigure cloud-init" fails with an error
[10:30] <CatKiller> When ran, it opens the curses menu correctly, I can for instance pick another source
[10:31] <CatKiller> but when I save, I get a few errors and the values of datasource_list remain unchangfed
[10:31] <CatKiller> Here's a paste of the errors
[10:31] <CatKiller> http://bpaste.net/show/nH2m5x3oKxGYP8cmrmBs/
[10:31] <CatKiller> dpkg-reconfigure returns "0" on exit though
[10:32] <CatKiller> Also the strange thing is that if I look in reconfigure, only the OpenStack datasource is selected.
[10:32] <CatKiller> But if I look into /etc/cloud/cloud.cfg.d/90_dpkg.cfg only CloudStack appears on the datasource_list
[17:21] <smoser> CatKiller, bug 1325746
[17:32] <CatKiller> smoser: Thanks!
[17:33] <smoser> i'm gonna upload that to proposed today
[17:34] <smoser> but it will be at least 7 days till its in trusty-proposed
[17:35] <CatKiller> Well I can probably compile and install cloud-init from source otherwise
[17:35] <CatKiller> purge the apt installed package
[17:35] <CatKiller> and just get the very latest
[17:35] <CatKiller> Also another question
[17:36] <CatKiller> I then changed /etc/cloud/cloud.cfg.d/90_dpkg.cfg "by hand" to include OpenStack and Ec2
[17:37] <CatKiller> However when I run "cloud-init init" it doesn't seem to try to connect to the metadata server
[17:37] <smoser> you can. but whenver dpkg-reconfigure cloud-init runs it screws it.
[17:37] <smoser> you probably have to run 'cloud-init init --local' first
[17:37] <CatKiller> Could that be that dpkg-reconfigure does more than just setting the metadata sources?
[17:37] <smoser> as that will remove some state
[17:39] <CatKiller> smoser: I'll try that too, thanks
[17:45] <CatKiller> smoser: omg it worked. Thanks a lot. Not sure what that did though ;)
[17:47] <smoser> CatKiller, sudo rm -f /var/lib/cloud/instance
[17:47] <smoser> is about it really.
[17:47] <smoser> since it had all ran before it found the 'None' data source. so running it again just said "already found".
[17:51] <CatKiller> ahhhh ok
[17:51] <CatKiller> smoser: I get it, I was wondering what all this data was about
[17:51] <CatKiller> smoser: So basically, in the base image that directoy
[17:51] <CatKiller> *directory should be empty
[17:52] <smoser> well, its a symlink
[17:52] <smoser> so it doesn't really  matter. 
[17:52] <smoser> when it finds a datasource, it links that tot he current data.
[17:52] <smoser> and other data is otherwise ignroed
[17:56] <CatKiller> smoser: OK cool, that makes a bit of sense
[17:57] <CatKiller> smoser: On a clean image, should I delete the entire contents of /var/lib/cloud then?
[17:57] <CatKiller> I've noticed that this directory only gets populated the first time cloud-init runs
[17:57] <CatKiller> So that I can leave cloud-init pick the "right" data source on boot?
[18:01] <smoser> you can.
[18:01] <smoser> you dont need to 
[18:02] <smoser> but you can
[18:02] <smoser> on boot, cloud-init --local gets run
[18:02] <smoser> so it will always pick the right datasource