https://docs.delftsolutions.nl/api.php?action=feedcontributions&feedformat=atom&user=Louisraymon1993Delft Solutions - User contributions [en]2026-04-03T22:09:55ZUser contributionsMediaWiki 1.39.3https://docs.delftsolutions.nl/index.php?title=WS_Proxmox_node_reboot&diff=229WS Proxmox node reboot2024-02-29T16:44:46Z<p>Louisraymon1993: </p>
<hr />
<div>== Tips & Notes ==<br />
* If you're expecting to reboot every node in the cluster, do the node with the containers last, to limit the amount of downtime and reboots for them<br />
* Updating a node: `apt update` and `apt full-upgrade`<br />
* Make sure all VMs are actually migratable before adding to a HA group<br />
* If there are containers on the device you are looking to reboot- you are going to need to also create a maintenance mode to cover them (for example teamspeak or stats)<br />
* Containers will inherit the OS of their host, so you will also need to handle triggers related to their OS updating, where appropriate <br />
<br />
== Pre flight checks ==<br />
* Check all Ceph pools are running on at least 3/2 replication<br />
* Check that all running VM's on the node you want to reboot are in HA (if not, add them or migrate them away manually)<br />
* Check that Ceph is healthy -> No remapped PG's, or degraded data redundancy<br />
<br />
== Reboot process ==<br />
* Start maintenance mode for the Proxmox node and any containers running on the node<br />
* Start maintenance mode for Ceph, specify that we only want to surpress the trigger for health state being in warning by setting tag `ceph_health` equals `warning`<br />
[[File:Ceph-maintenance.png|thumb]]<br />
* Set noout flag on host: `ceph osd set-group noout <node>`<br />
* '''Reboot''' node through web GUI<br />
* Wait for node to come back up<br />
* Wait for OSD's to be back online<br />
* Remove noout flag on host: `ceph osd unset-group noout <node>` ,to do this:<br />
<br />
# gain ssh access to host<br />
# Log in through IPA<br />
# Run the command<br />
<br />
* If a kernel update was done, manually execute the `Operating system` item manually to detect the update. Manually executing the two items that indicate a reboot is also usefull if they were firing, to stop them/check no further reboots are needed.<br />
* Ackowledge & close triggers<br />
* Remove maintenance modes<br />
<br />
== Aftercare ==<br />
* Ensure that Kaboom API is running on Screwdriver or Paloma. This is to get the best performance for the VM.</div>Louisraymon1993