Docker Community Forums

Share and learn in the Docker community.

Redeployment not working after I did an upgrade to 1.11.2-cs5


(Mwaaas) #1

Did an upgrade to 1.11.2-cs5 5 days ago and I have just noticed redeploying is failing.

Here are the logs :

Preparing to redeploy…
Inspecting tumacredo/apis:latest image in the registry
Image up to date in our database
Choosing best nodes…
Candidate node 80bdd2b8-40c7-4e8a-8b89-3babaa28166a.node.dockerapp.io. State: Deployed. Total num containers: 31. Num containers from this service: 9
Choosing node 80bdd2b8-40c7-4e8a-8b89-3babaa28166a.node.dockerapp.io because of the deployment strategy
Choosing best nodes…
Candidate node 80bdd2b8-40c7-4e8a-8b89-3babaa28166a.node.dockerapp.io. State: Deployed. Total num containers: 22. Num containers from this service: 0
Choosing node 80bdd2b8-40c7-4e8a-8b89-3babaa28166a.node.dockerapp.io because of the deployment strategy
Choosing node 80bdd2b8-40c7-4e8a-8b89-3babaa28166a.node.dockerapp.io because of the deployment strategy
Choosing node 80bdd2b8-40c7-4e8a-8b89-3babaa28166a.node.dockerapp.io because of the deployment strategy
Choosing node 80bdd2b8-40c7-4e8a-8b89-3babaa28166a.node.dockerapp.io because of the deployment strategy
Choosing node 80bdd2b8-40c7-4e8a-8b89-3babaa28166a.node.dockerapp.io because of the deployment strategy
Choosing node 80bdd2b8-40c7-4e8a-8b89-3babaa28166a.node.dockerapp.io because of the deployment strategy
Choosing node 80bdd2b8-40c7-4e8a-8b89-3babaa28166a.node.dockerapp.io because of the deployment strategy
Choosing node 80bdd2b8-40c7-4e8a-8b89-3babaa28166a.node.dockerapp.io because of the deployment strategy
Choosing node 80bdd2b8-40c7-4e8a-8b89-3babaa28166a.node.dockerapp.io because of the deployment strategy
Redeploying…
web-worker-5: Deploying in 80bdd2b8-40c7-4e8a-8b89-3babaa28166a.node.dockerapp.io
web-worker-5: Creating in 80bdd2b8-40c7-4e8a-8b89-3babaa28166a.node.dockerapp.io with docker name web-worker-5.tumacredo-prod.7a44dbd4
web-worker-5: Attaching container to overlay network dockercloud with ip 10.7.0.24
web-worker-5: Starting with docker id 92d1caa9bfda8a1a5ea9ee1e1d6c600983967e7534ac41264c23229361802d82 in 80bdd2b8-40c7-4e8a-8b89-3babaa28166a.node.dockerapp.io
ERROR: web-worker-5: NetworkDriver.Join: bridge “weave” not present; did you launch weave?
ERROR: Service Redeploy action on ‘web-worker’ (using ‘tumacredo/apis:latest’) has failed


(Mwaaas) #2

This is the second time am doing an upgrade then redeployment fails so frustrating


(Bernardo) #3

This is Bernardo from DockerCloud. We are having a look to your issue for nodes 816c8a0e-d75a-4526-b634-a97dd0130a44 and 80bdd2b8-40c7-4e8a-8b89-3babaa28166a. I’ll give you an update as soon as possible.


(Bernardo) #4

So node 80bdd2b8-40c7-4e8a-8b89-3babaa28166a seems to be working now (weave proxy container wasn’t running), can you give it a try?. For the node 816c8a0e-d75a-4526-b634-a97dd0130a44 it is already Terminated.

Regards,

Bernardo


(Mwaaas) #5

Its now working, but am starting to be afraid of upgrading the node, since the same issue has happened twice

Quick question: Is there any plan of docker-cloud start using docker swarm mode.


(Juanviola) #6

Hi Bernardo, I’m having the same issue on different nodes, this happens when I try to scale the service from docker-cloud cli. The error message is:

NetworkDriver.Join: bridge “weave” not present

I’ve scaled this service from 1 to 2, then 2 to 3, then 3 to 4 and started to get this error. After the error shows up can’t scale the service any more.

I’m running version 1.11.2-cs5

Thanks!