{"action":"closed","issue":{"url":"https://api.github.com/repos/cloudamatic/mu/issues/108","repository_url":"https://api.github.com/repos/cloudamatic/mu","labels_url":"https://api.github.com/repos/cloudamatic/mu/issues/108/labels{/name}","comments_url":"https://api.github.com/repos/cloudamatic/mu/issues/108/comments","events_url":"https://api.github.com/repos/cloudamatic/mu/issues/108/events","html_url":"https://github.com/cloudamatic/mu/issues/108","id":292497495,"node_id":"MDU6SXNzdWUyOTI0OTc0OTU=","number":108,"title":"Cannibalistic Mu Master","user":{"login":"ryantiger658","id":11201272,"node_id":"MDQ6VXNlcjExMjAxMjcy","avatar_url":"https://avatars1.githubusercontent.com/u/11201272?v=4","gravatar_id":"","url":"https://api.github.com/users/ryantiger658","html_url":"https://github.com/ryantiger658","followers_url":"https://api.github.com/users/ryantiger658/followers","following_url":"https://api.github.com/users/ryantiger658/following{/other_user}","gists_url":"https://api.github.com/users/ryantiger658/gists{/gist_id}","starred_url":"https://api.github.com/users/ryantiger658/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ryantiger658/subscriptions","organizations_url":"https://api.github.com/users/ryantiger658/orgs","repos_url":"https://api.github.com/users/ryantiger658/repos","events_url":"https://api.github.com/users/ryantiger658/events{/privacy}","received_events_url":"https://api.github.com/users/ryantiger658/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-01-29T17:40:54Z","updated_at":"2018-12-13T00:37:25Z","closed_at":"2018-12-13T00:37:25Z","author_association":"MEMBER","body":"A couple of things here:\r\n\r\n1. Should terminate running if mu-cleanup doesn't find a deployment with the given deployID. \r\n2. Should add guards to prevent cleaning up one's own mu-master\r\n3. I need to actually use syntactically valid commands. \r\n\r\n`[root@ip-10-0-4-244 demo]# mu-cleanup gitlab\r\nJan 29 17:05:12 - cleanup - I don't see a deploy named gitlab.\r\nJan 29 17:05:12 - cleanup - Can't load a deploy record for gitlab (#<Errno::ENOENT: No such file\r\nor directory @ dir_initialize - /opt/mu/var/deployments/gitlab>), cleaning up resources by guessw\r\nork\r\n[\"/opt/mu/lib/modules/mu/cleanup.rb:75:in `open'\",\r\n \"/opt/mu/lib/modules/mu/cleanup.rb:75:in `entries'\",\r\n \"/opt/mu/lib/modules/mu/cleanup.rb:75:in `run'\",\r\n \"/opt/mu/bin/mu-cleanup:59:in `<main>'\"]\r\n\r\n...\r\n\r\nJan 29 17:06:07 - cleanup - Missed some Chef resources in node cleanup, purging now\r\n**Jan 29 17:06:07 - groomers/chef - Deleting Chef resources associated with MU-MASTER\r\nJan 29 17:06:07 - groomers/chef - knife node delete MU-MASTER\r\nDeleted node[MU-MASTER]\r\nJan 29 17:06:07 - groomers/chef - knife client delete MU-MASTER\r\nDeleted client[MU-MASTER]\r\nJan 29 17:06:07 - groomers/chef - Deleting MU-MASTER: from vaults\r\nJan 29 17:06:07 - groomers/chef - Tried to delete vault MU-MASTER but got #<Net::HTTPServerExcept\r\nion: 404 \"Object Not Found\">, giving up**\r\nJan 29 17:06:08 - clouds/aws - Using AWS Security Group sg-c24a83b5\r\nJan 29 17:06:08 - clouds/aws - Adding current IP list to allow rule for port 10514 in sg-c24a83b5\r\nJan 29 17:06:08 - mommacat - Updating /opt/mu/var/nagios_user_home/.ssh/config...\r\nJan 29 17:06:09 - mommacat - Updating Nagios monitoring config, this may take a while...\r\nJan 29 17:06:14 - mommacat - Nagios monitoring config update complete.`"}}
{"actor":{"display_login":"ryantiger658"}}