Skip to content

Fix ssvm migrate stg net#13379

Draft
Pearl1594 wants to merge 1 commit into
4.20from
fix-ssvm-migrate-stgNet
Draft

Fix ssvm migrate stg net#13379
Pearl1594 wants to merge 1 commit into
4.20from
fix-ssvm-migrate-stgNet

Conversation

@Pearl1594

Copy link
Copy Markdown
Contributor

Description

This PR fixes: #13378

Types of changes

  • Breaking change (fix or feature that would cause existing functionality to change)
  • New feature (non-breaking change which adds functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • Enhancement (improves an existing feature and functionality)
  • Cleanup (Code refactoring and cleanup, that may add test cases)
  • Build/CI
  • Test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity

Bug Severity

  • BLOCKER
  • Critical
  • Major
  • Minor
  • Trivial

Screenshots (if appropriate):

How Has This Been Tested?

How did you try to break this feature and the system with this change?

@codecov

codecov Bot commented Jun 8, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 20.00000% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 16.26%. Comparing base (a3970bb) to head (7b680cf).

Files with missing lines Patch % Lines
...cloud/hypervisor/kvm/resource/BridgeVifDriver.java 20.00% 2 Missing and 2 partials ⚠️
Additional details and impacted files
@@             Coverage Diff              @@
##               4.20   #13379      +/-   ##
============================================
- Coverage     16.26%   16.26%   -0.01%     
+ Complexity    13434    13433       -1     
============================================
  Files          5666     5666              
  Lines        500645   500649       +4     
  Branches      60801    60804       +3     
============================================
- Hits          81426    81419       -7     
- Misses       410112   410121       +9     
- Partials       9107     9109       +2     
Flag Coverage Δ
uitests 4.14% <ø> (ø)
unittests 17.11% <20.00%> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR targets KVM SSVM live migration failures when the storage network uses a dedicated VLAN by ensuring the destination host creates the storage VLAN bridge during migration/network preparation, even when the NIC’s broadcastType is not Storage but the broadcastUri scheme indicates storage.

Changes:

  • Update BridgeVifDriver#createStorageVnetBridgeIfNeeded to detect storage networks via broadcastUri scheme (storage://...) in addition to broadcastType == Storage.
  • Avoid the previous early-return behavior that skipped bridge creation when broadcastType wasn’t Storage.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +189 to +197
if (nic.getBroadcastUri() == null) {
return storageBrName;
}

boolean isStorageBroadcast = Networks.BroadcastDomainType.Storage.equals(nic.getBroadcastType()) ||
Networks.BroadcastDomainType.Storage.equals(Networks.BroadcastDomainType.getSchemeValue(nic.getBroadcastUri()));
if (!isStorageBroadcast) {
return storageBrName;
}

@shwstppr shwstppr left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code lgtm

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

KVM: Live migration of SSVM fails with "Cannot get interface MTU" when storage network uses a dedicated VLAN

3 participants