[14:58] <smoser> natorious, hey. i can promise you some time later today, but the meeting in 2 minutes i can't really attend.
[14:59] <natorious> smoser: k, sounds good.
[15:23] <natorious> did find a bug w/ ephemeral disks that are not formatted w/ a filesystem in 0.7.x.  The mounts module seems to add an fstab entry thats invalid causing reboots to break in certain cases.
[15:24] <natorious> https://bugs.launchpad.net/cloud-init/+bug/1513109
[15:44] <smoser> natorious, clearly making reboot hang sucks
[15:44] <smoser> but if you declare a ephemeral disk, cloud-init assumes a filesystem on it.
[15:44] <smoser> but if mount fails, shoudl rpboably warn and not leave the fstab entry there.
[15:47] <natorious> right.  From a provider standpoint, secure erase would surely be done.  Our pub cloud ephemeral disks I believe come formatted ntfs too
[15:47] <natorious> it shouldn't be adding a raw block dev that isn't a partition to fstab thou
[15:48] <natorious> oh, I'll add some log data to that issue, one sec
[16:01] <flyinbut1s> Hello! Quick question...  when I'm creating a new image...  how do I tell cloud-init to run the init stuff on next boot?
[16:03] <natorious> flyinbut1s: if you build a new instance from that image, it should detect that its different and run everything as new
[16:04] <natorious> if your just testing things out, you can rm /var/lib/cloud and either reboot or run your init stages again
[16:04] <flyinbut1s> ahah, excellent. Wasn't clear if I had to toggle a flag somewhere or not.
[16:04] <flyinbut1s> thanks!
[16:04] <natorious> it tracks whats been ran via /var/lib/cloud/instances/{uuid}/data etc
[16:05] <natorious> so your datasource should be changing the instance info