Description of problem: Deploy templates to custom namespace and then delete templates from 'openshift' namespace, check templates page, no templates found. UI should show templates from this new custom ns. Version-Release number of selected component (if applicable): 4.10.0-0.nightly-2022-02-06-060618 How reproducible: 100% Steps to Reproduce: 1. change the common template namespace to "test" $ oc edit hco -n openshift-cnv kubevirt-hyperconverged spec: commonTemplatesNamespace: test 2. delete templates from "openshift". $ oc delete template --all -n openshift 3. check template page on UI Actual results: no template found Expected results: UI should render templates from namespace 'test' by reading commonTemplatesNamespace from HCO. Additional info:
HCO should have `commonTemplatesNamespace: openshift` by default, so UI can easily consume the value.
Adjust Expected results: UI should show templates in this custom namespace when user select this namespace on template list page.
Auto backport to 4.10 failed because of code confilct Cloning for 4.10 manually
The templates are showing in custom namespace now, but while creating VM from the template, it shows the error “Requested template could not be found“.
@yaacov After deploy the templates to custom namespace and without deleting templates in "openshift" ns, select custom ns, the UI still shows templates from "openshift" ns, is it an issue need to be fixed?
@Ruth Auto-update boot source is not available for templates in custom ns, should we support it? If yes, I guess the backend/ssp needs to support it firstly.
> @yaacov After deploy the templates to custom namespace and without deleting templates in "openshift" ns, select custom ns, the UI still shows templates from "openshift" ns, is it an issue need to be fixed? That is as design, if templates are available in "openshift" ns, they are visible from all namespaces ( this will change in 4.11 ) > @Ruth Auto-update boot source is not available for templates in custom ns, should we support it? If yes, I guess the backend/ssp needs to support it firstly. need a different bug > The templates are showing in custom namespace now, but while creating VM from the template, it shows the error “Requested template could not be found“. thanks will take car of that
(In reply to Yaacov Zamir from comment #10) > > @yaacov After deploy the templates to custom namespace and without deleting templates in "openshift" ns, select custom ns, the UI still shows templates from "openshift" ns, is it an issue need to be fixed? > > That is as design, if templates are available in "openshift" ns, they are > visible from all namespaces ( this will change in 4.11 ) > > > @Ruth Auto-update boot source is not available for templates in custom ns, should we support it? If yes, I guess the backend/ssp needs to support it firstly. > > need a different bug > https://bugzilla.redhat.com/show_bug.cgi?id=2055022
(In reply to Guohua Ouyang from comment #9) > @Ruth Auto-update boot source is not available for templates in custom ns, > should we support it? If yes, I guess the backend/ssp needs to support it > firstly. The templates reference boot sources in the same golden images namesapce and should work; can you explain what is missing?
(In reply to Ruth Netser from comment #13) > (In reply to Guohua Ouyang from comment #9) > > @Ruth Auto-update boot source is not available for templates in custom ns, > > should we support it? If yes, I guess the backend/ssp needs to support it > > firstly. > > The templates reference boot sources in the same golden images namesapce and > should work; can you explain what is missing? See bug: https://bugzilla.redhat.com/show_bug.cgi?id=2055022 After deploy the templates to a custom namespace, the boot source are missing.
The original issue is fixed in this bug, close the bug.