cfmorrell's Posts

Ultimately, I'm trying to write a PowerCLI script that will move my collection of templates between hosts by converting them to VMs, moving them, and then converting them back to templates.  I am una... See more...
Ultimately, I'm trying to write a PowerCLI script that will move my collection of templates between hosts by converting them to VMs, moving them, and then converting them back to templates.  I am unable to get past the first step, because none of my templates can be converted back to VMs.  Whether through the vCenter interface or through PowerCLI, i get a vim.fault.NotFound error with more detail of "The object or item referred to could not be found. vDS dvs port 51970 cannot be found."  I assume this is a DVS switch port that existed when the original VM was templatized, and may no longer exist.  See below for supporting logs.  Any thoughts? Chris   2021-01-04T22:26:52.232Z info vpxd[03619] [Originator@6876 sub=vpxLro opID=408cee58] [VpxLRO] -- BEGIN task-276953 -- vm-40781 -- vim.VirtualMachine.markAsVirtualMachine -- 526bc7cd-fc78-5692-bb77-2afba1bc5fa4(52fc23ca-26ad-514b-4657-2b7c1a0de405) 2021-01-04T22:26:52.238Z warning vpxd[03619] [Originator@6876 sub=vmmoVm opID=408cee58] New local path path for VM [vim.VirtualMachine:vm-40781,template-centos-6] is empty. Ignoring the change - vpxa will report the new path shortly 2021-01-04T22:26:52.246Z error vpxd[03619] [Originator@6876 sub=provisioning opID=408cee58] Unable to register template ds:///vmfs/volumes/5ab1058b-7d6e9626-ddb5-001018d6af90/template-centos-6/template-centos-6.vmtx as VM 2021-01-04T22:26:52.264Z error vpxd[03619] [Originator@6876 sub=SOAP-3 opID=408cee58] Method vim.VirtualMachine.markAsVirtualMachine threw undeclared fault of type vim.fault.NotFound 2021-01-04T22:26:52.264Z info vpxd[03619] [Originator@6876 sub=vpxLro opID=408cee58] [VpxLRO] -- FINISH task-276953 2021-01-04T22:26:52.264Z info vpxd[03619] [Originator@6876 sub=Default opID=408cee58] [VpxLRO] -- ERROR task-276953 -- vm-40781 -- vim.VirtualMachine.markAsVirtualMachine: vim.fault.NotFound: --> Result: --> (vim.fault.NotFound) { --> faultCause = (vmodl.MethodFault) null, --> faultMessage = (vmodl.LocalizableMessage) [ --> (vmodl.LocalizableMessage) { --> key = "com.vmware.vim.vpxd.dvs.portNotFound.label", --> arg = (vmodl.KeyAnyValue) [ --> (vmodl.KeyAnyValue) { --> key = "port", --> value = "51970" --> } --> ], --> message = <unset> --> } --> ] --> msg = "" --> } --> Args: --> --> Arg pool: --> 'vim.ResourcePool:resgroup-33696' --> Arg host: -->    
My issue is finally resolved.  Turned out that checksts.py was telling me that there weren't any issues, but there were four certificates (1 leaf and 3 roots).  I've read in a few places that there i... See more...
My issue is finally resolved.  Turned out that checksts.py was telling me that there weren't any issues, but there were four certificates (1 leaf and 3 roots).  I've read in a few places that there is only supposed to be one.  I ran fixsts.sh, which dropped me to 3 certs in checksts (1 root and 2 leaf certs).  After that, the vCLS machines showed up almost immediately.
Same result here.  I had to run stalefix, but everything is clear after that.  Still getting the "lack of suitable datastore" error.  Here are my lsdoctor -l results: root@vcsa1 [ ~/lsdoctor-master ... See more...
Same result here.  I had to run stalefix, but everything is clear after that.  Still getting the "lack of suitable datastore" error.  Here are my lsdoctor -l results: root@vcsa1 [ ~/lsdoctor-master ]# python lsdoctor.py -l ATTENTION: You are running a reporting function. This doesn't make any changes to your environment. You can find the report and logs here: /var/log/vmware/lsdoctor 2020-12-02T13:17:03 INFO main: You are reporting on problems found across the SSO domain in the lookup service. This doesn't make changes. 2020-12-02T13:17:03 INFO live_checkCerts: Checking services for trust mismatches... 2020-12-02T13:17:03 INFO generateReport: Listing lookup service problems found in SSO domain 2020-12-02T13:17:03 INFO generateReport: No issues detected in the lookup service entries for vcsa1.eecs.net (VC 7.0 or CGW). 2020-12-02T13:17:03 INFO generateReport: No issues detected in the lookup service entries for ##NO_HOSTNAME##. 2020-12-02T13:17:03 INFO generateReport: Report generated: /var/log/vmware/lsdoctor/vcsa1.eecs.net-2020-12-02-131703.json
Well that's a bummer.  I'm running an educational cluster with ~100 resource groups, ~1000 machines, way too may people touching vCenter, and we're in the middle of final project season.  I think I'm... See more...
Well that's a bummer.  I'm running an educational cluster with ~100 resource groups, ~1000 machines, way too may people touching vCenter, and we're in the middle of final project season.  I think I'm going to cross my fingers that everything remains stable as we limp through the last couple of weeks in the semester.  It's super exciting that VMWare put us in this situation though. 
Did you get anywhere on this?  I'm having the same issue and seeing the same errors in the EAM log.  I don't have a vSAN configured, so the VMWare docs don't appear to offer any thoughts.