Clarify KVM import template requirement#13126
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #13126 +/- ##
=========================================
Coverage 18.09% 18.09%
- Complexity 16721 16723 +2
=========================================
Files 6037 6037
Lines 542546 542546
Branches 66431 66431
=========================================
+ Hits 98159 98170 +11
+ Misses 433368 433355 -13
- Partials 11019 11021 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
|
@blueorangutan package kvm |
|
@andrijapanicsb a [SL] Jenkins job has been kicked to build packages. It will be bundled withkvm SystemVM template(s). I'll keep you posted as I make progress. |
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 17772 |
|
@blueorangutan test |
|
@andrijapanicsb a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
2 participants
Description
importUnmanagedInstancedocumentstemplateidas an optional parameter, but KVM unmanaged instance import currently requires a template and fails when one is not supplied.This updates the generated API parameter description for
templateidto explicitly mention that it is required when importing an unmanaged KVM instance. It avoids the current mismatch between API docs and runtime behavior without changing import semantics.Fixes #13067
Tests
Added
ImportUnmanagedInstanceCmdTestcoverage to verify thetemplateidAPI parameter description includes the KVM requirement.##########################################################
Generated by AI - do you REALLY think I became a Java developer overnight?
So, REVIEW PROPERLY and feel free to decline the PR if it's bunch of junk !
#########################################################