+++ This bug was initially created as a clone of Bug #2168486 +++

Description of problem:
"Restore template settings" is disabled while editing VM's CPU/Mem

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. create a vm from catalog
2. edit the VM's CPU/Mem
3.

Actual results:
"Restore template settings" is disabled

Expected results:
"Restore template settings" is enabled

Additional info:

— Additional comment from Hilda Stastna on 2023-03-01 01:56:47 CST —

Hi Guohua,

can you please, take a look at this? As this works as expected, in 4.13. "Restore template settings" is enabled and it does reset the settings to the templates' ones.
Thanks.

— Additional comment from Guohua Ouyang on 2023-03-01 09:25:08 CST —

I talked to Tal about the problem wasn't always happened, but when I checked it about 1 week ago, the problem is still happened.

I just find the root cause of the problem is the link of the VM's template is not correct, in the details tab of a VM which could see the issue, the link is '/k8s/ns/default/templates/rhel7-server-small', which should be '/k8s/ns/openshift/templates/rhel7-server-small'.

Reproduce steps:
1. Edit the boot source reference of RHEL7 template
2. Create a VM from RHEL7 template
3. "Restore template settings" is disabled in VM details tab
4. Click the template link, it does not open the template because it's not existing.

— Additional comment from Hilda Stastna on 2023-03-04 03:45:55 CST —

Note that with reproducing this bug, the following scenario occurs:
after clicking on "From template", when creating a VM from VirtualMachines list page, while "All projects" project/namespace set,
the namespace is changed to "default". IMO it should stay in "All Projects" namespace. WDYT, Guohua? Is that a bug, too? Thanks!

— Additional comment from Hilda Stastna on 2023-03-04 04:13:10 CST —

Also note that the root cause of this bug - incorrect link to the template in the VM's Details, is caused by the fact that when creating a VM,
the "label vm.kubevirt.io/template.namespace" is set incorrectly, its value is not the original template's namespace, but the VM's one.

— Additional comment from Guohua Ouyang on 2023-03-06 08:45:42 CST —

(In reply to Hilda Stastna from comment #3)
> Note that with reproducing this bug, the following scenario occurs:
> after clicking on "From template", when creating a VM from VirtualMachines
> list page, while "All projects" project/namespace set,
> the namespace is changed to "default". IMO it should stay in "All Projects"
> namespace. WDYT, Guohua? Is that a bug, too? Thanks!

While creating a pod under "All projects", it also changes to the ns "default".
So I would say let it be.