/srv/irclogs.ubuntu.com/2015/04/15/#cloud-init.txt

harlowjahttps://github.com/harlowja/cloud-init/tree/0.7.x-fixed should be the repo we need resynced...01:11
harlowjawith all the missing 0.7.x stuffs01:11
harlowja* https://github.com/stackforge/cloud-init/compare/0.7.x...harlowja:0.7.x-fixed01:12
=== harlowja is now known as harlowja_away
=== Guest87529 is now known as mwhudson
=== [1]claudiupopa is now known as claudiupopa
Odd_Blokesmoser: It does look like update_hostname is doing the right thing.11:11
Odd_Blokesmoser: I think I was hitting the cloud-init/walinuxagent race before.11:12
=== rangerpbzzzz is now known as rangerpb
smoserOdd_Bloke, https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1444086 seems kind of serious.13:30
smoseris someone looking at that ? 13:30
Odd_Blokesmoser: I believe utlemming has been.13:41
utlemmingsmoser: yeah, I14:45
utlemmingsmoser: er, I'm looking at that14:46
=== [1]claudiupopa is now known as claudiupopa
yaronr_hi guys15:37
yaronr_trying to add a yum_repos in cloud-init. installation fails because repo returns 40315:37
yaronr_interestingly, installation of packages that come from other repos fail as well15:37
ndoneganIt's going to be the server serving the repos that's returning 40315:39
ndoneganSo most likely you're pointing at the wrong directories for the repos, or there's some user or ip restriction on the repos.15:41
smoseror, if the repos are on S3, then 404 are returned as 40315:59
smoser(S3 does do that. ie, they tell you "you can't see that file", rather than 'that file doesnt exist')15:59
smoseryaronr_, ^15:59
yaronr_hmm16:00
yaronr_baseurl: http://repos.mesosphere.io/el/7/noarch/RPMS/mesosphere-el-repo-7-1.noarch.rpm16:00
yaronr_works on my browser..16:01
=== harlowja_away is now known as harlowja
zer0c00lhowdy17:51
smoserhi.17:52
kwapinghowdy17:54
harlowjakwaping hey, so i'm working with openstack-infra to get https://github.com/harlowja/cloud-init/tree/0.7.x-fixed pushed in to stackforge17:54
kwapingcool17:55
harlowjaand nm, https://github.com/stackforge/cloud-init/tree/0.7.x is up to date now17:55
harlowjalol17:55
harlowjasooo ya, thats done :-P17:55
kwapingwooo17:55
kwapingnew source of truth?17:55
kwapingso is the 0.7.x branch considered stable, and master is bleeding-edge?17:56
harlowjasure17:56
harlowjaseems about right17:56
kwapingha17:56
kwapingyeah, I like that scheme - was thinking about other options but that works for me17:57
harlowjaya, doesn't need to be perfect17:58
kwapingno, it needs to be perfect17:59
kwapingjk17:59
harlowjalol18:00
vilahi there !20:31
vilawith 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:34
viladoes that ring a bell ? 20:39
larsksvila: that pastebin apparently requires on to log in to view?20:49
vilaha right, sorry, bad habbit20:50
vilahttp://paste.ubuntu.com/10828856/20:51
larsksIt looks like there is no sshd-keygen service on vivid, at least.  20:59
larsksIt looks like key generation happens as part of the openssh-server postinst script...which is a terrible idea, but there it is.20:59
vilalarsks: you mean sshd-keygen exists somewhere else ?21:18
vilalarsks: and openssh-server may need to be fixed for vivid ?21:18
larsksvila: 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
larsksSomeone more familiar with the ubuntu side of things can probably provide a better answer. 21:23
vilaack, thanks21:23
vilasmoser, utlemming : any idea ?21:39
=== rangerpb is now known as rangerpbzzzz

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