This repository has been archived by the owner on Sep 18, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 49
segvault when updating / stuck updating #184
Comments
johanneswuerbach
changed the title
segvault when updating
segvault when updating / stuck updating
Aug 28, 2018
Looks like downgrading to v0.6.0 has solved the issue for us. |
The panic you are running into looks the same as the one in #93, which is odd because according to that issue, it should've been fixed with v0.7.0. I'll have to try and reproduce that, I don't remember much about it. As far as not updating, the panic shouldn't have anything to do with it, the panic comes because the dbus channel gets closed underneath the watch function because the system is going down for the reboot. Can you post the operator deployment for the failed one? Do you have a reboot window or any pre- or post-reboot hooks configured? It might also be helpful to get some of the debugging logs, which you can do by adding the flag |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Recently the CLUO (v0.7.0) seems to have been stuck and continuously tried to update the same node.
CoreOS:
CoreOS 1800.5.0
Kubernetes:
v1.9.9
Cloud:
AWS us-east-1, kops 1.10
Agent logs:
Controller logs:
The text was updated successfully, but these errors were encountered: