actcur-ansible/role-core
2
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions

Weekly reboot #4

New issue
Open
opened 2025-07-24 16:31:13 -05:00 by jayne · 2 comments
jayne commented 2025-07-24 16:31:13 -05:00
Owner
Copy link

Add a weekly reboot using systemd service/timer - day of week should be based on ansible id to reduce the number of VMs rebooting at the same time, should occur at 4am to minimize chance of causing an outage

Add a weekly reboot using systemd service/timer - day of week should be based on ansible id to reduce the number of VMs rebooting at the same time, should occur at 4am to minimize chance of causing an outage
jayne commented 2025-07-24 17:27:12 -05:00
Author
Owner
Copy link

Reboot should occur at 3:50am - to avoid conflict w/ ansible-update. That gives servers that run ansible-update at 3 or 4am plenty of time for both ansible (50 minutes) and the reboot (10 minutes).

Reboot should occur at 3:50am - to avoid conflict w/ ansible-update. That gives servers that run ansible-update at 3 or 4am plenty of time for both ansible (50 minutes) and the reboot (10 minutes).
jayne commented 2025-07-24 18:37:45 -05:00
Author
Owner
Copy link

Updates can be pulled out of core and into the reboot script. If done, updates should occur at 2am, reboot at 3:50am

When doing so, alma updates need to be handled as well.

Note: Ensure there is a delay of at least 3 days between ipa and ipa2 to reduce chance of both ending up in a failed state.

Updates can be pulled out of core and into the reboot script. If done, updates should occur at 2am, reboot at 3:50am When doing so, alma updates need to be handled as well. Note: Ensure there is a delay of at least 3 days between ipa and ipa2 to reduce chance of both ending up in a failed state.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
prod
v1.2
v1.1
v1.0
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: actcur-ansible/role-core#4
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?