ZSTAC-84636 backport VM HA orphaned skip-trace fix#4440
Conversation
Backport VM HA skip-trace protection to 5.4.10. 1. Why? When a management node leaves, its VM skip-trace entries are removed immediately. If those VMs are still being started by kvmagent, the next VM sync may treat them as stopped and trigger HA, causing split-brain. 2. How? Move departed management node skip entries into an orphaned set, keep them skipped for a configurable TTL, include them in VM sync skip lists, and remove expired entries with compare-and-remove cleanup. 3. Side effects? VMs whose controller MN departed stay skipped until the TTL expires. The default TTL is 600 seconds and can be changed by global config `kvm.vm.orphanedSkipTimeout`. # Summary of changes (by module): - kvm: add orphaned skip set, TTL global config, sync inclusion and CAS cleanup. Related: ZSTAC-84636 Related: ZSTAC-80821 Change-Id: I7862360c7318cedb51e38939467cf2a7836e61d0
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 36 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
Warning
|
Root cause:
When a management node leaves, its VM skip-trace entries are removed immediately. If kvmagent is still processing VM start operations from that management node, the next VM sync may see those VMs as stopped and trigger HA, causing split-brain.
Fix:
kvm.vm.orphanedSkipTimeoutwith default value600seconds.Verification:
git diff --checkmvn -pl plugin/kvm -am -DskipTests compileJira: ZSTAC-84636
Related: ZSTAC-80821
sync from gitlab !10401