Optional templateid param fails for KVM VM import

Open Beginner friendly
#13,067 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
java
Domain
documentation

Research direction

Start with the documented importUnmanagedInstance API and docs/en/4.22.0.0/adminguide/virtual_machines/importing_unmanaging_vms.html, then inspect UnmanagedVMsManagerImpl.java around lines 1605-1607 to confirm the KVM restriction. Check with maintainers whether the intended outcome is documentation-only or a code change; done means the API and administrator documentation accurately describe templateid behavior.

Written by the indexing model from the issue text.

Description

bug
problem

When importing a KVM VM via API and if a template is not specified, import fails with error,
Template is needed and unable to use default template for hypervisor KVM
Even though templateid parameter is specified as optional in the API documentation:
https://cloudstack.apache.org/api/apidocs-4.22/apis/importUnmanagedInstance.html

In UI, template is a required field though.

Image

Documentation doesn't talk about this restriction on KVM
https://docs.cloudstack.apache.org/en/4.22.0.0/adminguide/virtual_machines/importing_unmanaging_vms.html

This is more of a documentation issue if the following block can not be updated:
https://github.com/apache/cloudstack/blob/4.22.0.0/server/src/main/java/org/apache/cloudstack/vm/UnmanagedVMsManagerImpl.java#L1605-L1607

versions

4.22; Maybe other versions as well
Import VM

The steps to reproduce the bug

No response

What to do about it?

Either update the documentation or remove the restriction to use default dummy template.

Dominant language
Java
Stars
3.1k
Forks
1.4k
Avg merge
7d 5h
Merged PRs (30d)
28

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/cloudstack

All issues in apache/cloudstack

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.