Provisioning UCD agent from Blueprint Designer fails silently with: Agent did not show up even after agent_timeout_value seconds!
We are using UrbanCode Deploy and Blueprint Designer 6.2.5.
When provisioning a blueprint from Blueprint designer, the provisioning fails with: Resource CREATE failed: NameError: resources.component_name: Agent did not show up even after agent_timeout_value seconds!
I looked already at the help Troubleshooting deployments, increased the timeouts etc.
The HOT file section: ucd_agent_install_linux: contains
if ps -ef | grep -v grep | grep -q air-monitor.jar ; then
exit 0
elif [ -d /opt/ibm ]; then
exit 0
fi
if command -V apt-get && ! command -V curl; then apt-get -y install curl; fi
If I have a folder /opt/ibm, the script will exit with error code 0. In our case the VM had already such a folder.
Normally, you can see in /var/log/cloud-init.log:
Cloud-init v. 0.7.9 running 'modules:final' at Thu, 28 Sep 2017 09:31:42 +0000. Up 16.16 seconds.
/var/lib/cloud/instance/scripts/part-001: line 22: command: apt-get: not found
In the broken one, I can see:
2017-09-06 16:37:02,158 - __init__.py[DEBUG]: {'Content-Type': 'text/x-not-multipart', 'Content-Disposition': 'attachment; filename="part-001"', 'MIME-Version': '1.0'}
2017-09-06 16:37:02,158 - __init__.py[DEBUG]: Empty payload of type text/x-not-multipart
...
2017-09-28 09:03:15,394 - util.py[DEBUG]: Running command ['/var/lib/cloud/instance/scripts/part-001'] with allowed return codes [0] (shell=False, capture=False)
2017-09-28 09:03:15,529 - util.py[DEBUG]: Running command ['/var/lib/cloud/instance/scripts/runcmd'] with allowed return codes [0] (shell=False, capture=False)
Thus, we exited with error code 0.
I replaced in the HOT file the snipped above with:
if ps -ef | grep -v grep | grep -q air-monitor.jar ; then
exit 0
elif [ -d /opt/ibm ]; then
# exit 0
echo hello
fi
Like that the deployment could proceed, the agent got installed in the agent_timeout and the process did run.