-
Notifications
You must be signed in to change notification settings - Fork 43
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
After enabling a channel, it get's disabled after a few seconds #662
Comments
Without looking at the logs I think that sounds like "safe mode" being enabled. See this comment: #427 (comment) |
Ah yes, safe mode was indeed stopping further deployments.. Probably because all nodes are staying in "on hold" mode... So that's my next challenge. Figuring out why they are in on hold mode even though the machine itself say:
And the update-engine log is reporting omaha error:
So this part: Server logs:
I can't really see a clear reason for the errors... |
Well, this morning everything started upgrading again. I did nothing to make it that way.. soooo #magic ;-) |
In the instance view of Nebraska you should see the events that led to this but it requires finding the right instance. |
Description
After enabling a channel, a few seconds later the channel get's "disabled" without really giving me any hint as to why.
The logs are also not very clear to me. (see attached)
Impact
This means flatcar nodes do not get their upgrade fix ;-)
Environment and steps to reproduce
This is nebraska
2.7.0
installed in Kubernetes using the helm chart.Expected behavior
That the channel stay's enabled and hands out upgrades
The text was updated successfully, but these errors were encountered: