{"action":"created","issue":{"url":"https://api.github.com/repos/redhat-openstack/openshift-on-openstack/issues/49","repository_url":"https://api.github.com/repos/redhat-openstack/openshift-on-openstack","labels_url":"https://api.github.com/repos/redhat-openstack/openshift-on-openstack/issues/49/labels{/name}","comments_url":"https://api.github.com/repos/redhat-openstack/openshift-on-openstack/issues/49/comments","events_url":"https://api.github.com/repos/redhat-openstack/openshift-on-openstack/issues/49/events","html_url":"https://github.com/redhat-openstack/openshift-on-openstack/issues/49","id":136389079,"number":49,"title":"heat signaling?","user":{"login":"broskos","id":12814966,"avatar_url":"https://avatars.githubusercontent.com/u/12814966?v=3","gravatar_id":"","url":"https://api.github.com/users/broskos","html_url":"https://github.com/broskos","followers_url":"https://api.github.com/users/broskos/followers","following_url":"https://api.github.com/users/broskos/following{/other_user}","gists_url":"https://api.github.com/users/broskos/gists{/gist_id}","starred_url":"https://api.github.com/users/broskos/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/broskos/subscriptions","organizations_url":"https://api.github.com/users/broskos/orgs","repos_url":"https://api.github.com/users/broskos/repos","events_url":"https://api.github.com/users/broskos/events{/privacy}","received_events_url":"https://api.github.com/users/broskos/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-02-25T13:33:21Z","updated_at":"2016-02-25T13:54:04Z","closed_at":null,"body":"I seem to be having trouble with resources not signaling complete.  Using the HA setup, the lb completes, and the infra_host builds.  Looking in cloud-init logs I see everything completed successfully:\r\n\r\n + notify_success 'OpenShift node has been prepared for running ansible.'\r\nFeb 25 08:12:55 localhost cloud-init: + curl -i -X POST -H 'X-Auth-Token: df69949e37644d94a9a8345ae72b697b' -H 'Content-Type: application/json' -H 'Accept: application/json' http://10.12.32.10:8004/v1/be5e2313437b44f18c09889f571ae15d/stacks/my_openshift-infra_host-r6ypfk4jlz5p/ed63786b-8812-4f99-bcf5-071989ac7431/resources/wait_handle/signal --data-binary '{\"status\": \"SUCCESS\", \"reason\": \"OpenShift node has been prepared for running ansible.\", \"data\": \"OpenShift node has been prepared for running ansible.\"}'\r\n\r\nHowever the stack does not seem to advance, instead it stays 'create_in_progress'\r\ndeployment_tune_ansible   | 5363098c-fa5b-4807-938d-55fafaf47c24                                                | OS::Heat::SoftwareDeployment                                                                  | CREATE_IN_PROGRESS | 2016-02-25T13:06:51Z | infra_host      |\r\n\r\nIf I use heat resource-signal and manually signal that task as complete, it moves on to deploying the 3 masters, but they get stuck the same way after the work from cloud-init is done.\r\n\r\nAny ideas on what is going on here?"},"comment":{"url":"https://api.github.com/repos/redhat-openstack/openshift-on-openstack/issues/comments/188792008","html_url":"https://github.com/redhat-openstack/openshift-on-openstack/issues/49#issuecomment-188792008","issue_url":"https://api.github.com/repos/redhat-openstack/openshift-on-openstack/issues/49","id":188792008,"user":{"login":"broskos","id":12814966,"avatar_url":"https://avatars.githubusercontent.com/u/12814966?v=3","gravatar_id":"","url":"https://api.github.com/users/broskos","html_url":"https://github.com/broskos","followers_url":"https://api.github.com/users/broskos/followers","following_url":"https://api.github.com/users/broskos/following{/other_user}","gists_url":"https://api.github.com/users/broskos/gists{/gist_id}","starred_url":"https://api.github.com/users/broskos/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/broskos/subscriptions","organizations_url":"https://api.github.com/users/broskos/orgs","repos_url":"https://api.github.com/users/broskos/repos","events_url":"https://api.github.com/users/broskos/events{/privacy}","received_events_url":"https://api.github.com/users/broskos/received_events","type":"User","site_admin":false},"created_at":"2016-02-25T13:54:03Z","updated_at":"2016-02-25T13:54:03Z","body":"Jan - Thank you very much.  I'm missing heat-api-cfn server.  I'll get that\nturned up and should be fine.\n\nBrent Roskos\nSenior Cloud Architect\nCloud Practice\nRed Hat Consulting\n678-744-3623\n\n\nOn Thu, Feb 25, 2016 at 8:45 AM, Jan Provaznik <notifications@github.com>\nwrote:\n\n> deployment_tune_ansible is a SoftwareDeployment resource which is\n> triggered by os-collect-config service (heat agent running inside VM),\n> these sw deployments run in post cloud-init phase. If it's stuck in\n> IN_PROGRESS state, I can think of 2 reasons:\n> 1) cloud-init on infra host didn't finish yet for some reason - it's not\n> this case though based on the successful notify_success above\n> 2) os-collect-config on the infra node has issues running the\n> deployment_tune_ansible script. Could you please check \"journalctl -u\n> os-collect-config\" on the infra node - there should be a reason. Based on\n> the fact that the heat stack is stuck in IN_PROGRESS state for a while, my\n> guess would be that os-collect-config is failing to fetch instance metadata\n> from heat-api-cfn server -> is heat-api-cfn up and running in your\n> openstack deployment?\n>\n> —\n> Reply to this email directly or view it on GitHub\n> <https://github.com/redhat-openstack/openshift-on-openstack/issues/49#issuecomment-188789702>\n> .\n>\n"}}