=== harlowja is now known as harlowja_away
=== zz_gondoi is now known as gondoi
=== utlemming_kitche is now known as utlemming_mobile
[17:51] <lindenle> I/j #packer
=== harlowja_away is now known as harlowja
[21:22] <anotheral> i'd asked on tuesday about an AMI that won't populate ssh keys
[21:22] <anotheral> ~ubuntu has an empty authorized_keys file in the AMI, and it's not getting filled out when I launch an instance
[21:22] <anotheral> here's the log entry:
[21:22] <anotheral> Nov 20 21:15:41 ip-10-10-4-181 [CLOUDINIT] __init__.py[DEBUG]: handling ssh-import-id with freq=None and args=[]
[21:22] <anotheral> nothing after it
[21:31] <anotheral> full log is here: http://paste.ubuntu.com/9132258/
[21:32] <anotheral> and ec2metadata has the correct keys
[21:53] <sauce> which AMI? 12.04?
[21:54] <sauce> the cloud-init on the 12.04 is so old, mostly nothing works, so i basically use runcmd echo a ton.  "echo mydata >> /home/ubuntu/.ssh/authorized_keys" for example
[21:56] <anotheral> sauce: yeah, 12.04
[21:56] <anotheral> ok, that helps a bunch
[21:56] <sauce> thats your problem
[21:56] <anotheral> at least i'm not crazy
[21:56] <sauce> whatever ssh module you're using won't work
[21:56] <anotheral> guess i get to tell my users we're upgrading :-D
[21:57] <sauce> well before you do that, check out how 14.04 AMIs behave. i have no experience with 14.04 yet
[22:00] <anotheral> what I'm trying to do is just extend the base AMI with some company-specific stuff
[22:00] <sauce> oh. so take 12.04 and upgrade the cloud-init
[22:01] <sauce> then do your stuff
[22:01] <sauce> then AMI it
=== gondoi is now known as zz_gondoi