mirror of
https://github.com/PegaProx/project-pegaprox.git
synced 2026-04-25 10:05:56 +03:00
[GH-ISSUE #78] Host Maintenance #55
Labels
No labels
Approved
Q2-3 2026 Development
bug
documentation
enhancement
help wanted
invalid
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/project-pegaprox-PegaProx#55
Loading…
Add table
Add a link
Reference in a new issue
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?
Originally created by @Xerionty on GitHub (Feb 24, 2026).
Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/78
Originally assigned to: @MrMasterbay on GitHub.
When putting a host in maintenance balancing/automatic migration will migrate hosts back to the host entering maintenance. This behavior is also not detected by PegaProx. This results in displaying a host in maintenance which in reality is not the case.
Version Beta 0.6.6
2 node cluster
@MrMasterbay commented on GitHub (Feb 24, 2026):
Hi @Xerionty ,
do you have by any chance the native HA activated? I think this one here kinda starts to messing with the load balancing.
Otherwise please send us a support bundle under support@pegaprox.com
Best Regards,
Nico
@Xerionty commented on GitHub (Feb 24, 2026):
Hi @MrMasterbay native HA is indeed enabled and configured. What I normally would do to enter maintenance mode is to give the command
ha-manager crm-command node-maintenance enable pve02. This would move my VMs and CTs to the other host and when finished the host would go in maintenance. I do not know why I experience above described behavior because I would assume the same instructions are given when putting a host in maintenance via the PegaProx UI.@mkellermann97 commented on GitHub (Feb 24, 2026):
Hi @Xerionty ,
Responding on behalf of Nico as he's already asleep.
Currently, we handle this with our own logic. The native solution doesn't have an API for this, which means we'd need to trigger it manually via SSH. Due to the variety of different setups out there, we haven't included this yet – but we're adding it to our list for this week's update.
Regards,
Marcus
@Xerionty commented on GitHub (Feb 24, 2026):
Thank you for your time and consideration.
@Xerionty commented on GitHub (Feb 27, 2026):
Hey, thank you for your efforts. I upgraded to v0.9.0.1 but unfortunately this is still not working as intended. Is there something I can help troubleshoot with?
@mkellermann97 commented on GitHub (Feb 27, 2026):
Hi @Xerionty ,
Hm, that's odd. Could you send us a support bundle at support@pegaprox.com? We'll take a look.
I'll reopen this issue in the meantime.
Regards,
Marcus