=== cpaelzer_ is now known as cpaelzer === Odd_Blok1 is now known as Odd_Bloke === natorious_ is now known as natorious === jroll|dupe is now known as jroll === cbolt- is now known as cbolt === mgagne_ is now known as mgagne [18:57] Hello, I'm hitting an issue with systemd vs cloud-init. cloud-init runs as a systemd service. So when trying to start/stop services like docker from inside cloud-init scripts, the operation hangs in a deadlock. i.e. script waits for command to finish but command never finish as systemctl waiting for cloud-init to complete. The --no-block option is not helping as I don't only want to start a service but also interact with it and configure i [19:10] HI I made some changes to cloudinit package, deployed the debian file. How to restart the cloudinit service to see if my changes are reflected. I can do a simple reboot and check out. But wanted to know of a simple solution instead of a full reboot [19:31] akostadinov, hm.. can you give an example of exactly what you're doing ? [19:31] stanguturi, depending on waht you changed... [19:32] rm -Rf /var/lib/cloud/ /var/log/cloud-init* [19:32] then [19:32] cloud-init init --local [19:32] cloud-init init [19:32] cloud-init modules --mode=config [19:32] cloud-init modules --mode=final [19:33] or, if you just changed a config module [19:33] easiest thing to do is: [19:33] smoser: yes - starting docker service and pulling some images. It looks like docker-storage-setup service is required by the docker service and the docker storage-setup service should run after cloud-init finish. That's the deadlock issue. Read the man page and now trying to workaround this with systemctl --ignore-dependencies [19:34] cloud-init init single --name= --frequency=always [19:34] where 'name' is the name like 'cc_timezone' [19:35] smoser: it makes sense for services to run after cloud-init so that machine setup is done. But there's better mechanism to run scripts at different stages of boot process. So that one can execute proper initialization at proper times [19:36] @smoser: I changed some code in DataSourceOVF.py file. I want to restart the cloudinit service and see if my changes are loaded. [19:37] stanguturi, yeah, follow that above ^ [19:38] init --lcoal and then init [19:38] will run your ds [19:38] akostadinov, how are you doing that ? [19:39] via '#!' user-data or cloud-config install packages ? .. [19:39] smoser: [19:39] runcmd: [19:39] ... [19:39] - [ systemctl, enable, docker.service ] [19:39] - [ systemctl, start, docker-storage-setup.service, --ignore-dependencies ] [19:39] - [ systemctl, start, docker.service, --ignore-dependencies ] [19:39] ... [19:39] ah. k. so you installed it i suppose ? [19:40] smoser: yep, installed with packages:... [19:40] it should start on its own. shouldnt it ? [19:40] smoser: don't know, but it won't start before cloud-init finish either case [19:41] because docker-storage-setup should run after cloud-init final [19:42] oh. i see. [19:43] maybe drop a sytemd file that should start after docker.service [19:43] drop it in before installation (as a boothook perhaps) [19:43] and then it should start when it can on its own [20:02] smoser: how do I register a boothook? [20:02] bootcmd: [] [20:02] just like runcmd [20:03] is the easiest way [20:03] note, though, that boothooks run every boot [20:03] rather than once per instance [20:04] Hi I'm having a problem adding a yum repository to a CentOS #cloud-config , I am using yum_repos: … seeing "the requested URL returned error: 404.."… it works manually though [20:05] baseurl: http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm [20:06] smoser: you mean to do something like: [20:06] echo '...' > /etc/systemd/system/my.service [20:06] systemctl ... [20:06] correct? [20:07] am I missing any entries? I have specified PHP_epel: [20:07] baseurl:, enabled: true, name: some name, gpgcheck: false [20:08] never tried this before so excuse my ignorance.. [20:08] akostadinov, well, yeah. except i was saying you dont have to call systemctl [20:08] as if you've written the job correctly [20:09] it will start when docker.service is running [20:09] that make sense ? [20:09] harlowja_, ^ can you help out corb00 ? not sure myself. [20:10] hmmm [20:10] smoser: yes, that's my next bet if --ignore-dependencies fails. I guess I'd need `systemctl enable my.service` though.. or maybe it will be picket up automatically, never tried. I guess I'll just try [20:10] let's see here [20:10] thank you for suggestions [20:10] akostadinov, it should just pick it up automaticall [20:11] corb00 can u pastebin the yaml u are using, or gist [20:11] sure- give me a sec [20:15] here you go harlowia (had to switch machine) — http://pastebin.com/fftj7ayn [20:18] soooo [20:18] think i see it [20:18] http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm isn't the repo url, but is itself a repo file [20:21] ahhh - bloody beginner here, ok… [20:21] u want to use the url that is in that rpm [20:22] ok so just leave out the last bit.. [20:22] what that url is? :-P [20:23] http://paste.openstack.org/show/477195/ [20:23] wait I got you - ok… have to check whats in it :-) [20:23] pick 'http://download.fedoraproject.org/pub/epel/6/$basearch' [20:23] i think its ^ [20:23] or 'https://mirrors.fedoraproject.org/metalink?repo=epel-6&arch=$basearch' [20:23] not really sure, ha [20:23] one of those :-P [20:23] cool- let me try that… thanks harlowja!!