[GH-ISSUE #12] ❓ Issue/Improvement Request: Rolling Update restarts already up-to-date servers + fixed 5 min migration timeout #8

New issue

Closed

opened 2026-03-02 15:47:09 +03:00 by kerem · 3 comments

kerem commented

2026-03-02 15:47:09 +03:00

Owner

Originally created by @PhiGi87 on GitHub (Jan 27, 2026).
Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/12

Originally assigned to: @mkellermann97 on GitHub.

Summary

During Rolling Update, nodes that are already up-to-date are still being restarted instead of being skipped.
Additionally, the rolling update often fails with a timeout after 5 minutes if a host cannot migrate all VMs within that timeframe. For some hosts, VM migration can legitimately take longer.

Expected Behavior

Skip up-to-date servers (do not restart them if no update is required).
Rolling Update should allow longer migration durations when needed.
Ideally, the migration timeout should be configurable via settings (UI/config file/environment variable).

Actual Behavior

Servers that are already up-to-date are also restarted during Rolling Update.
Rolling Update can timeout after 5 minutes if VM migration is not finished in time.

I'm already thrilled with PegaProx =) Great work!

Originally created by @PhiGi87 on GitHub (Jan 27, 2026). Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/12 Originally assigned to: @mkellermann97 on GitHub. ### **Summary** During **Rolling Update**, nodes that are already **up-to-date** are still being restarted instead of being skipped. Additionally, the rolling update often fails with a **timeout after 5 minutes** if a host cannot migrate all VMs within that timeframe. For some hosts, VM migration can legitimately take longer. --- ### **Expected Behavior** - **Skip up-to-date servers** (do not restart them if no update is required). - Rolling Update should allow **longer migration durations** when needed. - Ideally, the **migration timeout should be configurable** via settings (UI/config file/environment variable). --- ### **Actual Behavior** - Servers that are already **up-to-date** are also **restarted** during Rolling Update. - Rolling Update can **timeout after 5 minutes** if VM migration is not finished in time. I'm already thrilled with PegaProx =) Great work!

kerem

2026-03-02 15:47:09 +03:00

closed this issue
added the
Approved
label

kerem commented

2026-03-02 15:47:10 +03:00

Author

Owner

@mkellermann97 commented on GitHub (Jan 27, 2026):

Hi @PhiGi87,
Thanks for the detailed report – that's really helpful.
I've looked into it and will address both issues:

Skipping up-to-date nodes – We'll implement a check to skip servers that don't require an update.
Migration timeout – We'll make the timeout configurable so it can be adjusted based on your environment.

These changes are planned for v0.6.2
Please note that changes need to be approved by @MrMasterbay, who is currently unavailable for health reasons. This may cause some delay.

Regards,
Marcus

@mkellermann97 commented on GitHub (Jan 27, 2026): Hi @PhiGi87, Thanks for the detailed report – that's really helpful. I've looked into it and will address both issues: Skipping up-to-date nodes – We'll implement a check to skip servers that don't require an update. Migration timeout – We'll make the timeout configurable so it can be adjusted based on your environment. These changes are planned for v0.6.2 Please note that changes need to be approved by @MrMasterbay, who is currently unavailable for health reasons. This may cause some delay. Regards, Marcus

kerem commented

2026-03-02 15:47:10 +03:00

Author

Owner

@mkellermann97 commented on GitHub (Jan 27, 2026):

@MrMasterbay request approved. Will be included with v0.6.2

@mkellermann97 commented on GitHub (Jan 27, 2026): @MrMasterbay request approved. Will be included with v0.6.2

kerem commented

2026-03-02 15:47:11 +03:00

Author

Owner

@mkellermann97 commented on GitHub (Jan 28, 2026):

Hi @PhiGi87 ,
Please check out the latest version.
Regards,
Marcus

@mkellermann97 commented on GitHub (Jan 28, 2026): Hi @PhiGi87 , Please check out the latest version. Regards, Marcus

kerem referenced this issue

2026-03-02 15:47:50 +03:00

[PR #8] [MERGED] fix: Adjust path evaluation to be executable from any dir #84