[01:11] https://github.com/harlowja/cloud-init/tree/0.7.x-fixed should be the repo we need resynced... [01:11] with all the missing 0.7.x stuffs [01:12] * https://github.com/stackforge/cloud-init/compare/0.7.x...harlowja:0.7.x-fixed === harlowja is now known as harlowja_away === Guest87529 is now known as mwhudson === [1]claudiupopa is now known as claudiupopa [11:11] smoser: It does look like update_hostname is doing the right thing. [11:12] smoser: I think I was hitting the cloud-init/walinuxagent race before. === rangerpbzzzz is now known as rangerpb [13:30] Odd_Bloke, https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1444086 seems kind of serious. [13:30] is someone looking at that ? [13:41] smoser: I believe utlemming has been. [14:45] smoser: yeah, I [14:46] smoser: er, I'm looking at that === [1]claudiupopa is now known as claudiupopa [15:37] hi guys [15:37] trying to add a yum_repos in cloud-init. installation fails because repo returns 403 [15:37] interestingly, installation of packages that come from other repos fail as well [15:39] It's going to be the server serving the repos that's returning 403 [15:41] So most likely you're pointing at the wrong directories for the repos, or there's some user or ip restriction on the repos. [15:59] or, if the repos are on S3, then 404 are returned as 403 [15:59] (S3 does do that. ie, they tell you "you can't see that file", rather than 'that file doesnt exist') [15:59] yaronr_, ^ [16:00] hmm [16:00] baseurl: http://repos.mesosphere.io/el/7/noarch/RPMS/mesosphere-el-repo-7-1.noarch.rpm [16:01] works on my browser.. === harlowja_away is now known as harlowja [17:51] howdy [17:52] hi. [17:54] howdy [17:54] kwaping hey, so i'm working with openstack-infra to get https://github.com/harlowja/cloud-init/tree/0.7.x-fixed pushed in to stackforge [17:55] cool [17:55] and nm, https://github.com/stackforge/cloud-init/tree/0.7.x is up to date now [17:55] lol [17:55] sooo ya, thats done :-P [17:55] wooo [17:55] new source of truth? [17:56] so is the 0.7.x branch considered stable, and master is bleeding-edge? [17:56] sure [17:56] seems about right [17:56] ha [17:57] yeah, I like that scheme - was thinking about other options but that works for me [17:58] ya, doesn't need to be perfect [17:59] no, it needs to be perfect [17:59] jk [18:00] lol [20:31] hi there ! [20:34] with a fresh vivid-server image and cloud-init 0.7.7 I end up with no ssh keys generated and suspicious messages in the console: https://pastebin.canonical.com/129649/ [20:39] does that ring a bell ? [20:49] vila: that pastebin apparently requires on to log in to view? [20:50] ha right, sorry, bad habbit [20:51] http://paste.ubuntu.com/10828856/ [20:59] It looks like there is no sshd-keygen service on vivid, at least. [20:59] It looks like key generation happens as part of the openssh-server postinst script...which is a terrible idea, but there it is. [21:18] larsks: you mean sshd-keygen exists somewhere else ? [21:18] larsks: and openssh-server may need to be fixed for vivid ? [21:23] vila: so, I'm not super familiar with the ubuntu openssh packages. *I* would fix this by having the sshd systemd service unit run a key-generation script prior to starting sshd. [21:23] Someone more familiar with the ubuntu side of things can probably provide a better answer. [21:23] ack, thanks [21:39] smoser, utlemming : any idea ? === rangerpb is now known as rangerpbzzzz