-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Upgrade of a Docker installation causes a panic, but restarts and is functional after restart #33685
Comments
@kinarashah Is this single docker install or HA install? |
Looks like single docker install. In my view this is not release blocker bug. What could happen in here is that when upgrading rancher, the rancher process was sent with SIGTERM, context are canceled and causing leader election to fail and have above logs. As long as it came back normal there is no problem with it. |
@StrongMonkey Yep, it was single node install. I agree this is not a release blocker because it restarts. @sowmyav27 suggested to still open this issue so we could keep track of it. |
I have the same problem on v1.19.16-rancher1-5, v1.19.16-rancher2-1 without rancher panel (cattle-system), pure k8s installed by rke on 3 nodes etcd,controlplane and 13 workers. I did not notice this problem on version v1.18.20-rancher1-3 . Scheduler is running with default configuration. The error only affects schedulers that are leaders. Scheduler doesn't just crash during k8s update, but every 10 minutes after becoming a leader, during normal operation. |
Upgraded rancher server from
v2.5.9
to master-head2f7d673b5193
. Saw the panic below in logs, container restarted and was fine later.The text was updated successfully, but these errors were encountered: