[10:33] <Odd_Bloke> smoser: I've submitted https://github.com/gabrielfalcao/HTTPretty/pull/238, which should fix the problem.
[12:48] <yaronr_> any reason why on gce, cloud-init would set hostname to 'localhost' instead of the machine id?
[13:02] <Odd_Bloke> yaronr_: No; anything in cloud-init.log to suggest what's happening?
[13:03] <yaronr_> i'm starting a new cluster now, i'll check the journald
[13:04] <yaronr_> problem is, there's too much going on there, separating the wheat from the chaff is challenging
[13:04] <Odd_Bloke> yaronr_: What distro?
[13:04] <yaronr_> coreos 612.1
[13:05] <yaronr_> using the same distro on aws doesn't have this problem
[13:05] <yaronr_> having all hostnames set to 'localhost' is a problem..
[13:05] <Odd_Bloke> yaronr_: What version of cloud-init?
[13:06] <yaronr_> how can I check?
[13:06] <yaronr_> best guess would be 1.3.3 
[13:09] <Odd_Bloke> yaronr_: `cloud-init --version` should do the trick.
[13:09] <yaronr_> :)
[13:13] <smoser> coreos is not this cloud-init
[13:14] <yaronr_> 'cloud-init: command not found'
[13:14] <Odd_Bloke> This conversation has followed the classic #cloud-init debugging pattern; I ask questions for a while and then smoser comes in with the right answer. :p
[13:15] <smoser> :)
[13:15] <smoser> but Odd_Bloke actually fixes things and writes good tests.
[13:15] <smoser> so he's good to hvae around
[13:16] <yaronr_> so.. how shall I debug the hostname issue then?
[13:17] <Odd_Bloke> yaronr_: Maybe ask in #coreos?
[13:17] <yaronr_> to paraphrase from star-trek: it's dead, jim...
[16:04] <harlowja_at_home>  yo yo, fyi i'm be out camping/hiking/biking/climbing today/tommorow, so don't cause to much trouble :)
[17:45] <smoser> harlowja_away, have fun. 
[22:30] <Linuturk> is there a way to phone_home a string?