<fix>[pci-device]: revert duplicate mdev ref cleanup - #4722
Conversation
Revert the schema cleanup added for ZSTAC-86456. 1. Why? The cleanup compares auto-increment IDs to choose the effective mdev spec, but ID order does not represent the currently active spec. 2. How? Remove the migration block introduced by b61dcd2. 3. Side effects? Duplicate references are no longer cleaned during the 5.4.12 upgrade. The linked issues are reopened for a corrected solution. # Summary of changes (by module): - db upgrade: remove the unsafe mdev reference cleanup. Related: ZSTAC-86456 Reverts: b61dcd2 Change-Id: I9cc698b3bf18d0e91bca16aaa12d5754d10db3d1
|
Warning Review limit reachedNext included review available in 24 minutes. View limit detailsLimit details: You’ve used the included review currently available. Your 60 included PR review attempts over the past 7 days set your current allowance at 1 review per hour. Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. Review configuration: ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
Warning
|
|
Comment from yaohua.wu: Review: MR !10778 — ZSTAC-86456Background (preserved across rounds)
FindingsNo actionable findings. Coverage
Verdict: APPROVEDThe MR is a focused revert with no unrelated changes. 🤖 Robot Reviewer |
ZSTAC-86456
Root Cause
The migration cleanup uses auto-increment
idordering to choose the effective mdev spec. The ID reflects the original reporting order and does not identify the currently active spec, so the cleanup can disable the spec that still has generated mdev devices.Changes
conf/db/upgradeb61dcd2442.Verification
git diff --checkpassed.b61dcd2442with no unrelated changes.Related MRs
bugfix/ZSTAC-86456@@2branch.Related: ZSTAC-86456
sync from gitlab !10778