/srv/irclogs.ubuntu.com/2015/08/25/#cloud-init.txt

=== zz_natorious is now known as natorious
=== natorious is now known as zz_natorious
smoserOdd_Bloke, i think "use sectors".13:40
Odd_Blokesmoser: Cool, that was my plan. :)13:41
smoserthe one annoyance is that i'm not 100% certain that sectors is always 512 bytes13:41
Odd_Blokesmoser: It looks like the reporting changes have broken the MAAS DataSource: https://launchpadlibrarian.net/215516689/cloud-init.log13:53
Odd_Blokesmoser: That's attached to https://bugs.launchpad.net/cloud-init/+bug/148850713:53
smoserOdd_Bloke, right . looking at that now.13:54
smoserfudge13:55
smoserthats a packaging thing13:55
smoseri think13:55
=== zz_natorious is now known as natorious
=== natorious is now known as zz_natorious
=== zz_natorious is now known as natorious
gamenamehi guys.  How can I tell in the main system log if cloud-init ran?18:40
gamenameor can I?18:40
kwadronaut'main'? usually you will want to check something like /var/log/cloud-init.log18:42
kwadronautand we're not all 'guys' ;-)18:42
gamenamekwadronaut: ok, but what if I can't access /var/log/cloud-* ??  Are there indicators in the main syslog to at least indicate cloud-init's ran?18:44
gamenamekwadronaut: The context is aws ec2 instances.  Getting the console log is easy.  Nothing else is.18:44
kwadronautboot log might have something, haven't looked at ec2 in a long time. stick around, someone else might know.18:46
gamenametks18:47
smosergamename, "main system log"20:02
smosersystemctl ?20:02
smoseror upstart20:02
gamenamesmoser: ok20:03
smoseri'm asking.20:03
smoserwhich were you using ?20:03
gamenamesmoser: neither.  I have an aws ec2 instance which I think may not have run the cloud init code.  But, I can only get access to the console log of the aws instance. Nothing more.  I'm locked out.  Was looking for hints as to how I can start debugging.20:04
gamenamesmoser: One option on aws is to get the console log.  That works.  Was hoping for some indication in it ...20:05
smosercan you post the console log ?20:06
smoserif its ubuntu you should see cloud-init writing things to it.20:06
gamenamesmoser: yes.  Standby ...20:06
gamenamesmoser: No, its CentOS 720:06
smoseri dont have a lot of experience there, testing a quick20:08
smoserheres a centos 6.6 with cloud-init: http://paste.ubuntu.com/12194874/20:08
smosersee cloud-init in that log20:08
gamenamesmoser: Here's the log https://gist.github.com/gamename/0407dccb5af2d35c606120:09
smoserand heres a 7 http://paste.ubuntu.com/12194878/20:09
smoserit'd seem likely that your networking didnt come pu20:09
smoserup20:09
smoseri guess.20:09
gamenamesmoser: yup.  Based on your examples, I think that's the case .20:10
smoserthe centos 7 log i showed is from a http://cloud.centos.org/centos/7/images/ image.20:11
smoseron openstack. i can't vouch for the correct (or useful) installation cloud-init on arbitrary ec2 image20:11
gamenamesmoser: Can they be imported into AWS as an AMI?20:11
gamenamesmoser: understood about vouching for the image.20:12
smosermaybe20:12
smoseri ran that one on a openstack.20:12
smoseri really dont know.20:12
smoseryou could use ubuntu :)20:12
smoserand our images "just work"20:12
gamenamesmoser: Sorry, I'm stuck with CentOS 7.  Lotsa reasons too icky to get into here.   Well, that's a start. Thanks.20:13
kwadronautor debian, and ask in #debian-cloud ;-)20:13
gamenamekwadronaut: Hmmmm ... there is a #centos-cloud channel I think.  Worth a query to them too...20:14
kwadronautgamename: i'm happy in my debian-ubuntu comfort zone.20:15
smosergamename, did you modify that image at all ?20:18
smoseror is it a "stock" image from some provider20:18
smoserif stock, then i'd ask the provider of the image20:19
=== natorious is now known as zz_natorious
=== zz_natorious is now known as natorious

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