mathiazsmoser: hi00:39
mathiazsmoser: is there already an AMI that has the fixed puppet cloud-init?00:39
=== erichammond1 is now known as erichammond
=== flaccid_ is now known as flaccid
=== flaccid_ is now known as flaccid
veenenenI'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:18
smoserveenenen, not been covered. i hadn't seen the announcemnt.14:59
smoserbut i think they should "just work"14:59
veenenenyeah, it may be amazon's fault15:00
veenenenpretty much, they launch fine, but when you restart them you can't log back in15:01
veenenenthere's no errors in the system log, so I'm not sure what's going on15:02
veenenenbut the service just launched today, so I figure a week or so to work out the bugs is ok15:02
smoserveenenen, i'll launch one and check it out.15:03
veeneneni saw an old error that talked about boots taking 240+ seconds, so that could be showing up again too15:03
veenenenalright, awesome, thanks15:03
smoseryeah, that is a rare timing thing15:03
smoserthat actually *coudl* be exposed more here on a slower system15:03
smoserbut i doubt thats it .15:03
smoseri suspect 'nobootwait' needs to be written somewhere in /etc/fstab15:03
smoserveenenen, do you want to know how to fix ?15:36
smoserin /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
smoserand its not going to be there.15:38
smoserso, the solution is to just delete that  entry, and reboot (i think) will work. testing reboot now.15:38
veenenenthat would explain it15:40
veenenenthat did it15:42
veenenenworked like a charm15:42
smosersudo sed -i.bk '/\/dev\/sda2/s,^,#,' /etc/fstab15:52
smoserfyi, i just opened https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/634102 to address t1.micro issues on reboot16:05
uvirtbotLaunchpad bug 634102 in cloud-init "t1.micro instances hang on reboot" [Undecided,New]16:05
_mup_Bug #634102: t1.micro instances hang on reboot <cloud-init (Ubuntu):New> <https://launchpad.net/bugs/634102>16:05
uvirtbotLaunchpad bug 634102 in cloud-init "t1.micro instances hang on reboot" [Undecided,New] https://launchpad.net/bugs/63410216: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
smosernice. uvirtbot and mup fight16:06
smoseryou got the last word, mup16:07
marruslHey #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
smoserhow did you supply the pre.seed ?17:38
marruslbooted 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:39
marruslso I leave just NC selected and continue, then that error.17:40
smoserbug you gve it a pre.seed17:49
smoserright ?17:49
marruslnope.  I just chose "install ubuntu enterprise cloud"...  sorry to throw you off... I just meant the CD version of the UEC install.17:52
marruslwhich does work off pre.seeds I thought... but no, nothing custom here, smoser.17:52
smoserwell, its not something i've seen, and i've not tried install of 10.04.1 media.17:53
smoserbut *someone* should have done that before release.17:53
smoserttx, ^17:53
marruslI'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
marrusler... i.e. "swap in 10.04 media and retry the NC install"17:55
veenenensmoser: 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:52
smoserveenenen, well there is no bootloader installed.20:53
smoserhttps://help.ubuntu.com/community/UEC/Images has informatoin on how to boot them with little hassle.20:54
smoser(maverick only, admittedly)20:54
veenenenSorry, I just found that page20:54
veenenensmoser: so do you really only get one boot off the maverick images before you have to push them up to ec2?23:10
=== erichammond1 is now known as erichammond

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!