Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rancher agent upgrade can cause previous agent to go dead, blocking upgrade of agent #10826

Closed
aemneina opened this issue Jan 11, 2018 · 1 comment
Assignees
Labels
area/agent Issues that deal with the Rancher Agent internal
Milestone

Comments

@aemneina
Copy link

Rancher versions:
rancher/server: 1.6.12
docker: 17.06
Somewhat related to: #9164 and moby/moby#21083 (comment)

I believe the rancher-agent-upgrade process doesnt wait long enough for the previous agent to exit. The agent upgrade then sends a sig-kill to the rancher agent process and then the agent process goes dead.

@sangeethah
Copy link
Contributor

Upgraded rancher server v1.6.12 having 20 nodes to v1.6.15-rc6.
Rancher agent in all nodes got upgraded successfully with out any issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/agent Issues that deal with the Rancher Agent internal
Projects
None yet
Development

No branches or pull requests

4 participants