{"action":"created","issue":{"url":"https://api.github.com/repos/coreos/bugs/issues/1475","repository_url":"https://api.github.com/repos/coreos/bugs","labels_url":"https://api.github.com/repos/coreos/bugs/issues/1475/labels{/name}","comments_url":"https://api.github.com/repos/coreos/bugs/issues/1475/comments","events_url":"https://api.github.com/repos/coreos/bugs/issues/1475/events","html_url":"https://github.com/coreos/bugs/issues/1475","id":166889927,"number":1475,"title":"Systemctl daemon-reload via cloud-config hoses my box","user":{"login":"rhiann0n","id":7799631,"avatar_url":"https://avatars.githubusercontent.com/u/7799631?v=3","gravatar_id":"","url":"https://api.github.com/users/rhiann0n","html_url":"https://github.com/rhiann0n","followers_url":"https://api.github.com/users/rhiann0n/followers","following_url":"https://api.github.com/users/rhiann0n/following{/other_user}","gists_url":"https://api.github.com/users/rhiann0n/gists{/gist_id}","starred_url":"https://api.github.com/users/rhiann0n/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rhiann0n/subscriptions","organizations_url":"https://api.github.com/users/rhiann0n/orgs","repos_url":"https://api.github.com/users/rhiann0n/repos","events_url":"https://api.github.com/users/rhiann0n/events{/privacy}","received_events_url":"https://api.github.com/users/rhiann0n/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2016-07-21T18:43:56Z","updated_at":"2016-07-21T19:06:05Z","closed_at":null,"body":"Hello,\r\n\r\nI am limited in what I can discuss via public channels, but I will state that I have a unique use case in which I must do a `systemctl daemon-reload` via a configuration management tool or via cloud-config.  When I try this method via cloud-config (via unit file), IE, running a `systemctl daemon-reload` as an `ExecStartPre=-` command in said unit file, systemd pukes.   Systemd pukes so hard that my box becomes hosed via log flooding, probably due to the inherent daemon reload nature of cloud-config and unit files or unit files themselves.   I was encouraged to file a bug on this.  See excerpts and examples below.  Please note I've omitted actual internal data and replaced them with random phrases:\r\n\r\nPlease let me know if you have any more questions or need more detail.  I'm running Coreos 10.10.\r\n\r\n### CoreOS Version ###\r\nCoreOS 10.10\r\n...\r\nBUG_REPORT_URL=\"https://github.com/coreos/bugs/issues\"\r\n\r\n### Environment ###\r\n\r\nWhat hardware/cloud provider/hypervisor is being used to run CoreOS?\r\n\r\n### Expected Behavior ###\r\ndaemon reload without quandary.\r\n\r\n### Actual Behavior ###\r\n```\r\nLOG EXCERPT OF HOSE.  (yes this box is intentionally tiny.\r\nJul 20 23:17:14 ip-awsinstance-region.compute.internal systemd[1]: Reloading.\r\nJul 20 23:17:15 ip-awsinstance-region.compute.internal systemd[1]: Reloading.\r\nJul 20 23:17:15 ip-awsinstance-region.compute.internal systemd[1]: Reloading.\r\nJul 20 23:17:15 ip-awsinstance-region.compute.internal systemd[1]: Reloading.\r\nJul 20 23:17:15 ip-awsinstance-region.compute.internal systemd[1]: Reloading.\r\nJul 20 23:17:15 ip-awsinstance-region.compute.internal systemd[1]: Reloading.\r\nJul 20 23:17:15 ip-awsinstance-region.compute.internal systemd[1]: Reloading.\r\nJul 20 23:17:15 ip-awsinstance-region.compute.internal systemd[1]: Reloading.\r\nJul 20 23:17:15 ip-awsinstance-region.compute.internal systemd[1]: Reloading.\r\nJul 20 23:17:15 ip-awsinstance-region.compute.internal systemd[1]: Reloading.\r\nJul 20 23:17:15 ip-awsinstance-region.compute.internal systemd[1]: Reloading.\r\nJul 20 23:17:15 ip-awsinstance-region.compute.internal systemd[1]: Reloading.\r\nJul 20 23:17:16 ip-awsinstance-region.compute.internal systemd[1]: Reloading.\r\nJul 20 23:17:16 ip-awsinstance-region.compute.internal systemd[1]: Reloading.\r\nJul 20 23:17:16 ip-awsinstance-region.compute.internal systemd[1]: Reloading.\r\nJul 20 23:17:16 ip-awsinstance-region.compute.internal systemd[1]: Reloading.\r\nJul 20 23:17:16 ip-awsinstance-region.compute.internal systemd[1]: Reloading.\r\nJul 20 23:17:16 ip-awsinstance-region.compute.internal systemd[1]: Reloading.\r\nJul 20 23:17:16 ip-awsinstance-region.compute.internal systemd[1]: Reloading.\r\nJul 20 23:17:16 ip-awsinstance-region.compute.internal systemd[1]: Reloading.\r\nJul 20 23:17:16 ip-awsinstance-region.compute.internal systemd[1]: Reloading.\r\nJul 20 23:17:16 ip-awsinstance-region.compute.internal systemd[1]: Reloading.\r\nJul 20 23:17:16 ip-awsinstance-region.compute.internal systemd[1]: Reloading.\r\nJul 20 23:17:16 ip-awsinstance-region.compute.internal systemd[1]: Reloading.\r\nJul 20 23:17:17 ip-awsinstance-region.compute.internal systemd[1]: Reloading.\r\nJul 20 23:17:17 ip-awsinstance-region.compute.internal systemd[1]: Reloading.\r\nJul 20 23:17:17 ip-awsinstance-region.compute.internal systemd[1]: Reloading.\r\nJul 20 23:17:17 ip-awsinstance-region.compute.internal systemd[1]: Reloading.\r\nJul 20 23:17:17 ip-awsinstance-region.compute.internal systemd[1]: Reloading.\r\nJul 20 23:17:17 ip-awsinstance-region.compute.internal systemd[1]: Reloading.\r\n```\r\n\r\n### Reproduction Steps ###\r\n\r\nCreate a systemd unit file via bash that triggers a config management platform and put a systemd daemon reload in cloud config as seen below.\r\n\r\n```\r\n#######Offending part of cloud-config\r\n####Really important that I run this via another automation platform, use-case I cannot give inherent details about, but it's an intentional part of our architecture.\r\n  - \"command\": |-\r\n      start\r\n    \"content\": |-\r\n      [Unit]\r\n      Description=Bootstrap Stuff\r\n      After=bootstrap-otherstuff.service\r\n      [Service]\r\n      ExecStartPre=/bin/bash -c '/bin/sh -x /tmp/bootstrap branch test' (all this does is write a unit file which I cannot restart on the CoreOs box via this process.)\r\n      ExecStartPre=/usr/bin/systemctl daemon-reload     \r\n      ExecStart=/usr/bin/systemctl start bootstrap-evenmorethings.service\r\n      ExecStop=/usr/bin/systemctl stop bootstrap-evenmorethings.service\r\n    \"name\": |-\r\n      bootstrap-thething.service\r\n```\r\n\r\n## Feature Request ##\r\nappears to be a systemd bug or cloud-config bug.\r\n\r\n### Environment ###\r\ntest\r\n\r\nWhat hardware/cloud provider/hypervisor is being used to run CoreOS?\r\nAWS\r\n### Desired Feature ###\r\n\r\n### Other Information ###\r\n@marineam has assisted in the past.\r\n"},"comment":{"url":"https://api.github.com/repos/coreos/bugs/issues/comments/234352301","html_url":"https://github.com/coreos/bugs/issues/1475#issuecomment-234352301","issue_url":"https://api.github.com/repos/coreos/bugs/issues/1475","id":234352301,"user":{"login":"rhiann0n","id":7799631,"avatar_url":"https://avatars.githubusercontent.com/u/7799631?v=3","gravatar_id":"","url":"https://api.github.com/users/rhiann0n","html_url":"https://github.com/rhiann0n","followers_url":"https://api.github.com/users/rhiann0n/followers","following_url":"https://api.github.com/users/rhiann0n/following{/other_user}","gists_url":"https://api.github.com/users/rhiann0n/gists{/gist_id}","starred_url":"https://api.github.com/users/rhiann0n/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rhiann0n/subscriptions","organizations_url":"https://api.github.com/users/rhiann0n/orgs","repos_url":"https://api.github.com/users/rhiann0n/repos","events_url":"https://api.github.com/users/rhiann0n/events{/privacy}","received_events_url":"https://api.github.com/users/rhiann0n/received_events","type":"User","site_admin":false},"created_at":"2016-07-21T19:06:04Z","updated_at":"2016-07-21T19:06:04Z","body":"@mischief  Can you point me to the best AMI to use?"}}
{"actor":{"display_login":"rhiann0n"}}