#Ansible module for rolling reboot

1 messages · Page 1 of 1 (latest)

rigid compass
#

Do we have any ansible module supported node reboot,

The checking process can be done by rest/info module
such as cluster show, node show, storage failover show and whether the network interfaces are home or not.

But the takeover and giveback process?
ex:
storage failover takeover -ofnode <nodename>
storage failover giveback -ofnode <nodename> -override-vetoes true

If using command module, there is a confirmation that need to type "y" to be done, I think this doesn't support in ansible

carmine pagoda
#

If you don't mind me asking; what is the use case here?
I find it very rare to need to reboot a node.

sinful sorrel
rigid compass
#

@carmine pagoda When the system is down and cannot find the solution, reboot might help.

#

@sinful sorrel I prefer using "storage failover takeover" than "node reboot"

sinful sorrel
#

I agree if you have a choice. But there is no API endpoint for takeover. And reboot does the same thing if HA is active

rigid compass
#

@sinful sorrel Thanks for this help!
I will try to use restit module with that URL!

rigid compass
#

@sinful sorrel From the document, it says using PATCH method with action value setting to "reboot" and then "giveback"?
I don't see the "action" attribute in the info model

sinful sorrel
#

I also rely on the documention here. 🤷‍♂️ Why should the action be in the info model?

rigid compass
#

@sinful sorrel the PATCH request body

rigid compass
#

@sinful sorrel Is there API for “storage failover giveback -ofnode <nodename> -override-vetoes true”?
If I use command module, how can I bypass the -override-vetoes confirmation notice?

buoyant lava
#

though i don't see any storage failover listed in that guide, let me check i if i can find it

rigid compass
#

@buoyant lava I can use the na_ontap_command command to run "storage failover giveback -ofnode <nodename> -override-vetoes true", but how can I bypass the second confirmation
Is the ansible.builtin.expect module works>

buoyant lava
#

Let me check, i think we had a way around this but not 100% sure

rigid compass
#

@buoyant lava I tried with na_ontap_command, and it seems working, but not sure does it just bypass the confirmation automatically as default?

buoyant lava
#

Sorry it been a long time since i've used this module for this specific thing. I"m still checking to see how we get around this, but i believe if there a second confirmation we will hang on it or timeout on it.