Skip to content

<fix>[cbt]: add temporary volume mapping migration - #4634

Open
ZStack-Robot wants to merge 1 commit into
5.5.30from
sync/yingzhe.hu/fix/ZSTAC-85010-5.5.30@@2
Open

<fix>[cbt]: add temporary volume mapping migration#4634
ZStack-Robot wants to merge 1 commit into
5.5.30from
sync/yingzhe.hu/fix/ZSTAC-85010-5.5.30@@2

Conversation

@ZStack-Robot

Copy link
Copy Markdown
Collaborator

Jira

  • ZSTAC-85010

Summary

  • Add CbtTaskTemporaryVolumeVO schema in V5.5.30__schema.sql.
  • Migrate legacy CBT scratch-volume refs out of CbtTaskResourceRefVO while preserving duplicate scratch volumes for cleanup.
  • Re-create source-volume refs in CbtTaskResourceRefVO and keep source/task FKs restrictive to avoid losing cleanup metadata before scratch volumes are deleted.

Validation

  • PASS: git diff --check
  • BLOCKED: mvn -pl cbt,test-premium -am -Dtest=TestCbtTaskCase -DfailIfNoTests=false test failed before reaching CBT because 5.5.30 local baseline cannot compile zstack-iam2 (RoleMutationExtensionPoint unresolved).
  • BLOCKED: mvn -pl test-premium -Dtest=TestCbtTaskCase -DfailIfNoTests=false test failed in full test source compile due unrelated missing classes in volumeCache/zwatch/ai/iam2/license/zbs tests.

Pair MR

  • premium: pending

sync from gitlab !10608

ZSTAC-85010

Change-Id: I2b36a21b2b71be408d156b3be8f15f3f15637222
@coderabbitai

coderabbitai Bot commented Jul 22, 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: 48 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: Path: http://open.zstack.ai:20001/code-reviews/zstack-cloud.yaml (via .coderabbit.yaml)

Review profile: CHILL

Plan: Pro

Run ID: 39c0d7d9-ca1a-490e-a3f2-27aef271585c

📥 Commits

Reviewing files that changed from the base of the PR and between 73136a1 and bea2390.

📒 Files selected for processing (1)
  • conf/db/upgrade/V5.5.30__schema.sql
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch sync/yingzhe.hu/fix/ZSTAC-85010-5.5.30@@2

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