2
edits
WS Proxmox node reboot: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
* 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 | * 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 | ||
* Updating a node: `apt update` and `apt full-upgrade` | * Updating a node: `apt update` and `apt full-upgrade` | ||
* Make sure all VMs are actually migratable before adding to a HA group | |||
== Pre flight checks == | == Pre flight checks == | ||
| Line 16: | Line 17: | ||
* Wait for node to come back up | * Wait for node to come back up | ||
* Wait for OSD's to be back online | * Wait for OSD's to be back online | ||
* Remove noout flag on host: `ceph osd unset-group noout <node>` | * Remove noout flag on host: `ceph osd unset-group noout <node>` ,to do this: | ||
Log in through IPA | # gain ssh access to host | ||
Run | # Log in through IPA | ||
# Run the command | |||
* 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. | * 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. | ||
* Ackowledge & close triggers | * Ackowledge & close triggers | ||