Can't get slave out of maintenance mode after yum updates
-
I started off attempting to change the pool master. The console said it changed, however xcp-ng center would not connect. It finally connected and is fine in xcp-ng center however the console on the new master shows no management network, no nics.
Part two:
I though that it errored out so I put one of the slaves in maintenance mode (classic rookie screw up on my part) and did a yum update and rebooted. Now I can't get that slave out of maintenance mode. I'm trying to minimize my issues here but what should I do. Do I need to change pool masters yet again, move vms, do yum updates on it and reboot? -
@rustylh Not a pro here, but in my experience thus far, most weird issues are solved with a Toolstack Restart. Have you tried that already? If not, do so from whichever node is currently the master, then report back.
-
- About the xsconsole: sometimes it's not refreshing. You can try to get access to the console, then type "xsconsole" it will start it and you should see it works
- You must have the master up to date if you want your slave to connect again. I never tried to elect a new master in the middle of the upgrade, I would discourage it. Better shutdown some VMs on the master, upgrade it and you are automatically back on track.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login