Skip to content

<fix>[ha]: ZSTAC-84992 direct-pick HA pre-fence core to 5.4.12 (@@3)#4561

Open
MatheMatrix wants to merge 3 commits into
5.4.12from
sync/yingzhe.hu/cp/5.4.12/ZSTAC-84992-direct-pick-20260714@@3
Open

<fix>[ha]: ZSTAC-84992 direct-pick HA pre-fence core to 5.4.12 (@@3)#4561
MatheMatrix wants to merge 3 commits into
5.4.12from
sync/yingzhe.hu/cp/5.4.12/ZSTAC-84992-direct-pick-20260714@@3

Conversation

@MatheMatrix

Copy link
Copy Markdown
Owner

Summary

Backport the ZSTAC-84992/ZSTAC-83890 HA pre-fence core changes to 5.4.12 by direct cherry-pick.

Changes

  • Adds core pre-fence system tag handling and peer requirement for suspect-host HA start.
  • Updates VM start-on-hypervisor flow and HA start message/extension contract.

Cherry-picked commits

  • e6d9f59 <fix>[ha]: stabilize suspect host pre-fence flow
  • 3845ee6 <fix>[ha]: create pre-fence tag in core
  • b894009 <fix>[ha]: require peer for pre-fence tag

Testing

  • git diff --check upstream/5.4.12..HEAD

Resolves: ZSTAC-84992

sync from gitlab !10528

huhu0316 added 3 commits July 14, 2026 11:32
Move premium-only HA pre-fence details out of community while keeping the generic async before-start extension point support.

Jira: ZSTAC-83890

Test: mvn -pl header,compute,plugin/kvm,simulator/simulatorImpl,testlib -DskipTests compile

Change-Id: I168adf82338f9df9e76287619b7f76a8e5be695f
Move HA pre-fence pending tag creation into HaStartVmInstanceMsg handling after the VM state update, so later pre-fence execution observes the same database state.

Resolves: ZSTAC-83890

Change-Id: I7f046732e0245319ed4cf188d1342b65dad11767
Create HA pre-fence pending tag only when the checker provides an accessible peer host.

The peer should be covered by the HA dead-host and storage-inactive paths, so do not persist a fallback marker when it is absent.

Resolves: ZSTAC-83890

Change-Id: I36426b3386f1080ddeae8396ea9c4f7a81e25711
@coderabbitai

coderabbitai Bot commented Jul 14, 2026

Copy link
Copy Markdown

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 24 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: fe9fef39-f2b7-43e7-ad4d-4b7616c8b834

📥 Commits

Reviewing files that changed from the base of the PR and between dc33d7f and b894009.

📒 Files selected for processing (5)
  • compute/src/main/java/org/zstack/compute/vm/VmInstanceBase.java
  • compute/src/main/java/org/zstack/compute/vm/VmStartOnHypervisorFlow.java
  • compute/src/main/java/org/zstack/compute/vm/VmSystemTags.java
  • header/src/main/java/org/zstack/header/vm/HaStartVmInstanceMsg.java
  • header/src/main/java/org/zstack/header/vm/VmBeforeStartOnHypervisorExtensionPoint.java

Warning

.coderabbit.yaml has a parsing error

The CodeRabbit configuration file in this repository has a parsing error and default settings were used instead. Please fix the error(s) in the configuration file. You can initialize chat with CodeRabbit to get help with the configuration file.

💥 Parsing errors (1)
Could not fetch remote config from http://open.zstack.ai:20001/code-reviews/zstack-cloud.yaml: TimeoutError: The operation was aborted due to timeout
⚙️ Configuration instructions
  • Please see the configuration documentation for more information.
  • You can also validate your configuration using the online YAML validator.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch sync/yingzhe.hu/cp/5.4.12/ZSTAC-84992-direct-pick-20260714@@3

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants