Deep Debroy

@manixx If you navigate to the Deployment under the resource group in the Azure portal, do you see any errors? From your description of symptoms it seems very likely the...

Well that's a very interesting error. It seems to indicate that somehow you tried to deploy the default template associated with the independent Docker4Azure VMs rather than the Docker4Azure swarm...

If you do not see any `ManualUpgrade` events, I would guess the upgrade script issued the overall deployment upgrade API call but Azure simply returned success but failed a bit...

Thank you @manixx and appreciate your help and feedback with investigating the issue.

I did find a bug where VM enumeration from the Azure side seems to have changed slightly leading to none of the upgrades actually taking place - the upgrade script/container...

@tisoft thanks for reporting the multi deployment scenario. I will look at providing a way to the user to select the deployment they want upgraded.

@netflash to get rid of the nodes marked `Down`, you can issue a `docker node rm` from the manager to remove them for the stack. We will enhance things a...

@netflash does the above compose file start up fine in other stacks? Can you share the `docker-compose-traefik.yml` file? I see that docker did not create any replica at all and...

@netflash I was just going through the docker engine logs from your diagnostics uploads earlier. From the logs for `traefik_military_com_private` I found the service ID is `tozjaj6xh6j3`. ```docker service ls.stdout:tozjaj6xh6j3...

@davidwneary you need to insert the key in the `/home/docker/.ssh/authorized_keys` file inside the `docker4x/agent-azure` container. So you need something along the lines of: ```swarm-exec docker exec agent /bin/bash -c "cmd"...