Description of problem: As for the attached screenshots, all the templates are visible in the developer catalog and the user can potentially try to instantiate them from the UI. But in order to really get a working virtual machine the user should provide the name of an existing PVC which contains the OS disk so the feature (?) is basically unusable and just confusing. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. go to the developer catalog and try to start a VM from one of the templates listed there 2. 3. Actual results: you can instantiate the template to a real VM just if you already have an existing PVC and you know its reference Expected results: - the feature is completed (at least for upstream OS I can choose from a list of images and let CDI import them) - or the VM templates are completely hidden from the developer catalog Additional info: I don't know if we already have any annotation to hide a template from the developer catalog or if we need some change also at UI level
Created attachment 1668137 [details] Templates in developer catalog
Created attachment 1668138 [details] Create a VM from the template
Thanks for raising this Simone. We should understand if the templates can be hidden from the catalog with an annotation. Please pear in mind that moving them to a different namespace will hide them as well, but will probably break the UI (which is expecting them in a specific namespace).
A template can be hidden from the UI by adding the 'hidden' tag.
Verify VM don't appear in developer catalog Kubevirt: v0.30.1
Created attachment 1698802 [details] developer calatog
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:3194