rancher: Rancher 2.3.3 update can't create new node template to use existing vsphere template

What kind of request is this (question/bug/enhancement/feature request): BUG

Steps to reproduce (least amount of steps as possible):

upgraded from Rancher 2.3.2 to 2.3.3
old templates still work
new templates cant find resource pool, same resource pool from old template Please select a new value. The following is no longer valid: “/SAC3/host/DES/Resources/bktest”
created node template pointing at “deploy from template: data center” gets the following error [node-controller] failed with : Error creating machine: Error in driver during machine creation: vm ‘SAC3/vm/DES//SAC3/vm/DES/Templates/rhel77_k8_d1934_overlay2_nov28’ not found

Result: looks like the vsphere targeting is not working for resource pools and it looks like its duplicating the folder location for locating the template

Other details that may be helpful:

Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): 2.3.3
Installation option (single install/HA): single

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported):
Machine type (cloud/VM/metal) and specifications (CPU/memory):
Kubernetes version (use kubectl version):

the cluster does not create because of the node templates not working correctly

Docker version (use docker version):

N/A

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 3
Comments: 18 (5 by maintainers)

Most upvoted comments

Just want to say I’m having the same issue. If more info is needed I’m happy to help troubleshoot.

soostdijck on Nov 29, 2019

I am experiencing the exact same problems as the original poster. After upgrade to 2.3.3, templates are broke if I update them. Old ones that I don’t update still work. I see the same problems as documented up top. I can provide any details as needed. Thankfully I discovered this on a test cluster, but I have definitely found that as soon as a Rancher node template is updated, it no longer works.

EDIT: I should add that creating a new template from scratch has the exact same problem.

EDIT2: I viewed one template that hadn’t been updated and another that had in the API and here are a couple differences in paths used.

Pre-Update (works):

“folder”: “/dev-k8s”,
“hostsystem”: “Cluster/esx1.domain.com”,
“pool”: “”,

Post-Update (doesn’t work):

“folder”: “/Datacenter/vm/dev-k8s”,
“hostsystem”: “/Datacenter/host/Cluster/esx1.domain.com”,
“pool”: “/Datacenter/host/Cluster/Resources”,

It’s adding “/Datacenter/vm” and “/Datacenter/host/” to those paths where previously it wasn’t there and was working. For the record, my datacenter is called “Datacenter”, cluster is just “Cluster” and I have no resource pools aside form what is default.

espigle on Dec 5, 2019

@Tejeev An even better way to save your sanity: Change folder to “/foldername” instead of “”, will actually work as you expected it to in the first place.

NahmiiVuhuni on Dec 19, 2019

We worked around the issue by doing the following:

Go to your node templates
Choose View in API in the ellipsis menu for your chosen node template
Select Edit in the Operations menu on the right
Check for and correct full paths in the vmwarevsphereConfig section to be vsphere syntax simple paths. I believe you will need to remove /##Redacted##/vm and /##Redacted##/host anywhere you see it. Also replace null with "" everywhere you see it in this field to avoid https://github.com/rancher/rancher/issues/2451.
Select Show Request
And if all looks good, you can choose to Send Request

Tejeev on Jan 2, 2020

Ive got same issue, but not seems is duplicated path, the error is Error creating machine: Error in driver during machine creation: vm ‘C1/vm/RANCHER//C1/vm/INFRA/TEMPLATES-C1/centos.template’ not found Where RANCHER is my Resource Pool (where cluster should be created) and the second path is the template location

ldibello on Dec 3, 2019