While the deployment was a success, Docker Cloud could not successfully use the webhook callback, resulting in an error for the notification services(like Slack).
The request was made to:
POST /api/app/v1/service/service_hash/trigger/trigger_hash/call/
I’m not really sure what to do, it looks like a bug at your end.
So the webhook callback is still failing as shown in these timeline entries:
[6/28/2016, 2:33:38 PM]web-1: Creating in NODE_HASH.node.dockerapp.io with docker name CONTAINER_NAME
[6/28/2016, 2:33:39 PM]web-1: Starting with docker id CONTAINER_ID in NODE_HASH.node.dockerapp.io
[6/28/2016, 2:33:40 PM]web-1: Running in NODE_HASH.node.dockerapp.io
[6/28/2016, 2:33:40 PM]Service Redeploy (trigger) action on 'web' (using 'mycompany/myimage:latest') has finished successfully
[6/28/2016, 2:33:40 PM]Webhook callback failed: 400 Client Error: BAD REQUEST for url: https://registry.hub.docker.com/u/mycompany/myimage/hook/HOOK_HASH/
However, the Slack notification bot is now sending ‘success’ messages, instead of failures, which is sufficient in my case.