Fix stg access group validation#13562
Conversation
* VM Migration: Storage access groups validation issue fix * Refactor list empty checks --------- Co-authored-by: Sachin R Doddaguni <s_rudrappadoddagu@apple.com>
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## 4.22 #13562 +/- ##
=========================================
Coverage 17.69% 17.69%
Complexity 15833 15833
=========================================
Files 5925 5925
Lines 533534 533551 +17
Branches 65273 65274 +1
=========================================
+ Hits 94394 94437 +43
+ Misses 428463 428434 -29
- Partials 10677 10680 +3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
This pull request has merge conflicts. Dear author, please fix the conflicts and sync your branch with the base branch. |
…stg-access-group-validation
…stg-access-group-validation
|
@blueorangutan package |
|
@Pearl1594 a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
|
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 18597 |



Description
The PR fixes the below issue:
VM migration fails with “Storage access groups on the source and destination hosts did not match” if list of storage access groups does not match.
Steps to reproduce:
Expected result:
VM migrated as there is common storage access group, where ROOT volume created from (aced).
Observed result:
Storage access groups on the source and destination hosts did not match.
It just simply checks collections [legacy, aced] and [aced] should be equal.
Types of changes
Feature/Enhancement Scale or Bug Severity
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
How did you try to break this feature and the system with this change?