-
Notifications
You must be signed in to change notification settings - Fork 413
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
Rebooting after: "Updating machineconfig from {hash} to {same-hash}" #224
Comments
So looks like somebody is editing the file I would guess |
Ah, that's probably what's going on. That image-registry line is not here. Looks like the DNS operator. I'll file an issue over there. |
/cc @crawford @aaronlevy as more people changing configuration on disk and will end up stepping on each other and if you step on MCD it will keep rebooting nodes.... :( |
Closing this in favor of openshift/cluster-dns-operator#63 |
Do not taunt happy fun MCD :p. |
Poking around on master-0 during this run:
It's possible that the underlying issue is due to whatever took down the initial etcd-member pod (751acc223850b, I'm still looking into this), but I don't understand why the MCD keeps going after:
Is the issue the
selfLink was empty, can't make reference
? It seems surprising to trigger a reboot because you failed to submit an event. Some previous discussion of reboot triggers in #199, but I don't understand either that issue or this one clearly enough to want to attempt to tie them together ;). @cgwalters comment about identical configs seems like this issue though.The text was updated successfully, but these errors were encountered: