Repository navigation
Conversation
|
@blueorangutan package |
|
@nvazquez 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 19538 |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## 4.22 #14395 +/- ##
=========================================
Coverage 18.01% 18.02%
- Complexity 16265 16274 +9
=========================================
Files 5936 5936
Lines 536395 536401 +6
Branches 65701 65704 +3
=========================================
+ Hits 96658 96708 +50
+ Misses 428710 428664 -46
- Partials 11027 11029 +2
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:
|
| addInstanceToGroup(id, group); | ||
| } else if (group != null) { | ||
| // Allow removing an instance from its group when passing an empty group on update | ||
| removeInstanceFromInstanceGroup(vm.getId()); |
There was a problem hiding this comment.
should the api doc for group say an empty value takes the instance out of its group? cmk and terraform users wont find it otherwise
| addInstanceToGroup(id, group); | ||
| } else if (group != null) { | ||
| // Allow removing an instance from its group when passing an empty group on update | ||
| removeInstanceFromInstanceGroup(vm.getId()); |
There was a problem hiding this comment.
can we add a unit test for the empty group case? this new path isnt covered
|
Thanks @Damans227 - review comments addressed @blueorangutan package |
|
@nvazquez 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 19541 |
|
@blueorangutan test |
|
@nvazquez a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
Description
This PR fixes a limitation on the instance groups functionality. Once a VM was added to an instance group, it was not possible to remove it from the group (the workaround was updating the
instance_group_vm_maptable or removing the VM)This fix allows passing an empty
groupparameter on theupdateVirtualMachineAPI to remove the VM from its current instance groupTypes of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
Tested updating VM group via UI to existing instance groups and to the empty field to remove the VM from its current group.
How did you try to break this feature and the system with this change?