[00:39] <mathiaz> smoser: hi
[00:39] <mathiaz> smoser: is there already an AMI that has the fixed puppet cloud-init?
[14:18] <veenenen> I'm sure this has been covered already, but has there been any progress on figuring out what's going on with the ubuntu ebs images and amazon's new micro instances?
[14:59] <smoser> veenenen, not been covered. i hadn't seen the announcemnt.
[14:59] <smoser> but i think they should "just work"
[15:00] <veenenen> yeah, it may be amazon's fault
[15:01] <veenenen> pretty much, they launch fine, but when you restart them you can't log back in
[15:02] <veenenen> there's no errors in the system log, so I'm not sure what's going on
[15:02] <veenenen> but the service just launched today, so I figure a week or so to work out the bugs is ok
[15:03] <smoser> veenenen, i'll launch one and check it out.
[15:03] <veenenen> i saw an old error that talked about boots taking 240+ seconds, so that could be showing up again too
[15:03] <veenenen> alright, awesome, thanks
[15:03] <smoser> yeah, that is a rare timing thing
[15:03] <smoser> that actually *coudl* be exposed more here on a slower system
[15:03] <smoser> but i doubt thats it .
[15:03] <smoser> i suspect 'nobootwait' needs to be written somewhere in /etc/fstab
[15:36] <smoser> veenenen, do you want to know how to fix ?
[15:38] <smoser> in /etc/fstab, you'll have an entry for /dev/sda2, which isn't present. mountall will run wait indefinitely for a device /dev/sda2 to appear on next boot.
[15:38] <smoser> and its not going to be there.
[15:38] <smoser> so, the solution is to just delete that  entry, and reboot (i think) will work. testing reboot now.
[15:40] <veenenen> great
[15:40] <veenenen> that would explain it
[15:42] <veenenen> that did it
[15:42] <veenenen> worked like a charm
[15:42] <veenenen> thanks
[15:52] <smoser> sudo sed -i.bk '/\/dev\/sda2/s,^,#,' /etc/fstab
[16:05] <smoser> fyi, i just opened https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/634102 to address t1.micro issues on reboot
[16:05] <_mup_> Bug #634102: t1.micro instances hang on reboot <cloud-init (Ubuntu):New> <https://launchpad.net/bugs/634102>
[16:05] <_mup_> Bug #634102: t1.micro instances hang on reboot <cloud-init (Ubuntu):New> <https://launchpad.net/bugs/634102>
[16:05] <_mup_> Bug #634102: t1.micro instances hang on reboot <cloud-init (Ubuntu):New> <https://launchpad.net/bugs/634102>
[16:06] <_mup_> Bug #634102: t1.micro instances hang on reboot <cloud-init (Ubuntu):New> <https://launchpad.net/bugs/634102>
[16:06] <smoser> nice. uvirtbot and mup fight
[16:07] <smoser> you got the last word, mup
[17:37] <marrusl> Hey #ubuntu-cloud.  question:  I'm installing a node controller using the pre.seed (cd install) method and got this error just after selecting to install the server as a Node Controller:
[17:37] <marrusl> http://i52.tinypic.com/2ymu4oy.jpg
[17:38] <smoser> how did you supply the pre.seed ?
[17:39] <marrusl> booted 10.04.01 media and selected "install uec".  the install says it has detected a cloud controller, would you like to install a NC?
[17:40] <marrusl> so I leave just NC selected and continue, then that error.
[17:49] <smoser> bug you gve it a pre.seed
[17:49] <smoser> right ?
[17:52] <marrusl> nope.  I just chose "install ubuntu enterprise cloud"...  sorry to throw you off... I just meant the CD version of the UEC install.
[17:52] <marrusl> which does work off pre.seeds I thought... but no, nothing custom here, smoser.
[17:52] <smoser> ok.
[17:53] <smoser> well, its not something i've seen, and i've not tried install of 10.04.1 media.
[17:53] <smoser> but *someone* should have done that before release.
[17:53] <smoser> ttx, ^
[17:55] <marrusl> I'll see if I can get someone to swap in 10.04 GA media and see what happens.  The CLC/walrus/sc/cc is on one machine and was built with 10.04.01 for what it's worth.
[17:55] <marrusl> er... i.e. "swap in 10.04 media and retry the NC install"
[20:52] <veenenen> smoser: I've been trying to get the ec2 images to boot today, and am still not able to get it to work. I booted a blank vm into gparted and dd'd the lucid image to a sda1 partition on the new virtual drive, set the boot flag and repaired the file system. I checked the fstab and made sure that matched up. I then restart the vm, but it just sits there when it gets to "Booting from Hard Disk"
[20:53] <smoser> veenenen, well there is no bootloader installed.
[20:54] <smoser> https://help.ubuntu.com/community/UEC/Images has informatoin on how to boot them with little hassle.
[20:54] <smoser> (maverick only, admittedly)
[20:54] <veenenen> Sorry, I just found that page
[20:54] <veenenen> thanks
[23:10] <veenenen> smoser: so do you really only get one boot off the maverick images before you have to push them up to ec2?