Upgraded to 1.10 and go-machine won't start

Archive Rancher 1.x
1

I upgraded to version 1.10 of Rancher, running in a HA cluster of three nodes with docker 1.10.3. Everything seemed to upgrade just fine however the go-service will not start. It keeps rebuilding the containers. The following is what is in the logs for the container

time="2016-07-05T18:52:25Z" level=info msg="Listening on 0.0.0.0:80"
time="2016-07-05T18:52:25Z" level=info msg="Forwarding setup to: :80"
time="2016-07-05T18:52:26Z" level=info msg="Listening on port: 80"
time="2016-07-05T18:52:26Z" level=info msg="Setting log level" logLevel=info
time="2016-07-05T18:52:26Z" level=info msg="Starting go-machine-service..." gitcommit=v0.31.6
time="2016-07-05T18:52:26Z" level=info msg="Waiting for handler registration (1/2)"
time="2016-07-05T18:52:43Z" level=fatal msg="Exiting go-machine-service: Timed out waiting for transtion."
time="2016-07-05T18:52:43Z" level=fatal msg="exit status 1"
time="2016-07-05T18:54:59Z" level=info msg="Listening on 0.0.0.0:80"
time="2016-07-05T18:54:59Z" level=info msg="Forwarding setup to: :80"
time="2016-07-05T18:55:00Z" level=info msg="Listening on port: 80"
time="2016-07-05T18:55:00Z" level=info msg="Setting log level" logLevel=info
time="2016-07-05T18:55:00Z" level=info msg="Starting go-machine-service..." gitcommit=v0.31.6
time="2016-07-05T18:55:00Z" level=info msg="Waiting for handler registration (1/2)"
time="2016-07-05T18:55:17Z" level=fatal msg="Exiting go-machine-service: Timed out waiting for transtion."
time="2016-07-05T18:55:17Z" level=fatal msg="exit status 1"