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