03-06-2020 07:11 AM
We have a customer who's grid upgrade got "stuck" when the active node of the grid master tried to upgrade. Passive node got upgraded ok and then failover occured, but the active node (which is now passive) did not reboot properly and now appears to be corrupt. All other nodes in the grid have been upgraded apart from this one.
Customer is trying to sort out an RMA but in the meantime is trying to add new nodes to the grid, however they get error messages stating that new nodes can't be added until the upgrade has been completed. Grid upgrade screen shows that the grid master has not completed upgrading - is there a way (maybe via a secret CLI command) to tell NIOS to abort the upgrade so that the customer can add these new nodes to the grid?
I'll log a ticket with support if no-one knows here, I just need to find out the serial number.
PCN (UK) Ltd
All opinions expressed are my own and not representative of PCN Inc./PCN (UK) Ltd. E&OE
03-30-2022 08:50 AM - edited 03-31-2022 12:40 AM
I know this is a very old threat, and you probably already got your answer from Support. But for google search purposes I thought it would be useful to comment on this one.
And correct me if I'm wrong, but I thought this should be done by entering the following command in the CLI:
set grid_upgrade forced_end
A good post about this by adhill: https://community.infoblox.com/t5/Trending-KB-Articles/344-How-to-stop-Scheduled-upgrade-forcefully-...