[13:40] <smoser> Odd_Bloke, i think "use sectors".
[13:41] <Odd_Bloke> smoser: Cool, that was my plan. :)
[13:41] <smoser> the one annoyance is that i'm not 100% certain that sectors is always 512 bytes
[13:53] <Odd_Bloke> smoser: It looks like the reporting changes have broken the MAAS DataSource: https://launchpadlibrarian.net/215516689/cloud-init.log
[13:53] <Odd_Bloke> smoser: That's attached to https://bugs.launchpad.net/cloud-init/+bug/1488507
[13:54] <smoser> Odd_Bloke, right . looking at that now.
[13:55] <smoser> fudge
[13:55] <smoser> thats a packaging thing
[13:55] <smoser> i think
[18:40] <gamename> hi guys.  How can I tell in the main system log if cloud-init ran?
[18:40] <gamename> or can I?
[18:42] <kwadronaut> 'main'? usually you will want to check something like /var/log/cloud-init.log
[18:42] <kwadronaut> and we're not all 'guys' ;-)
[18:44] <gamename> kwadronaut: 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] <gamename> kwadronaut: The context is aws ec2 instances.  Getting the console log is easy.  Nothing else is.
[18:46] <kwadronaut> boot log might have something, haven't looked at ec2 in a long time. stick around, someone else might know.
[18:47] <gamename> tks
[20:02] <smoser> gamename, "main system log"
[20:02] <smoser> systemctl ?
[20:02] <smoser> or upstart
[20:03] <gamename> smoser: ok
[20:03] <smoser> i'm asking.
[20:03] <smoser> which were you using ?
[20:04] <gamename> smoser: 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:05] <gamename> smoser: One option on aws is to get the console log.  That works.  Was hoping for some indication in it ...
[20:06] <smoser> can you post the console log ?
[20:06] <smoser> if its ubuntu you should see cloud-init writing things to it.
[20:06] <gamename> smoser: yes.  Standby ...
[20:06] <gamename> smoser: No, its CentOS 7
[20:08] <smoser> i dont have a lot of experience there, testing a quick
[20:08] <smoser> heres a centos 6.6 with cloud-init: http://paste.ubuntu.com/12194874/
[20:08] <smoser> see cloud-init in that log
[20:09] <gamename> smoser: Here's the log https://gist.github.com/gamename/0407dccb5af2d35c6061
[20:09] <smoser> and heres a 7 http://paste.ubuntu.com/12194878/
[20:09] <smoser> it'd seem likely that your networking didnt come pu
[20:09] <smoser> up
[20:09] <smoser> i guess.
[20:10] <gamename> smoser: yup.  Based on your examples, I think that's the case .
[20:11] <smoser> the centos 7 log i showed is from a http://cloud.centos.org/centos/7/images/ image.
[20:11] <smoser> on openstack. i can't vouch for the correct (or useful) installation cloud-init on arbitrary ec2 image
[20:11] <gamename> smoser: Can they be imported into AWS as an AMI?
[20:12] <gamename> smoser: understood about vouching for the image.
[20:12] <smoser> maybe
[20:12] <smoser> i ran that one on a openstack.
[20:12] <smoser> i really dont know.
[20:12] <smoser> you could use ubuntu :)
[20:12] <smoser> and our images "just work"
[20:13] <gamename> smoser: Sorry, I'm stuck with CentOS 7.  Lotsa reasons too icky to get into here.   Well, that's a start. Thanks.
[20:13] <kwadronaut> or debian, and ask in #debian-cloud ;-)
[20:14] <gamename> kwadronaut: Hmmmm ... there is a #centos-cloud channel I think.  Worth a query to them too...
[20:15] <kwadronaut> gamename: i'm happy in my debian-ubuntu comfort zone.
[20:18] <smoser> gamename, did you modify that image at all ?
[20:18] <smoser> or is it a "stock" image from some provider
[20:19] <smoser> if stock, then i'd ask the provider of the image