vLCM - An unexpected error has occured.

[barnette08]

Hey all,

In my lab environment I've started kicking the tires of vSphere Lifecycle Manager and I'm running into this weird issue that's rendering it nonfunctional.

I can create a cluster image without an issue, but after I upload the PowerPathVE add-on component, vLCM comes up with the below error.  I even went through the process of reimaging and redeploying vCenter just to sanity check and unfortunately I've ended up with the same result.  Interestingly, I can still manage the cluster image and remediate hosts from the hosts and clusters view but if I try to go to vLCM everything is blank and I get the error.

Anyone else hitting this? Any ideas?

[vTara]

Hi barnette08,

You can try to stop html5 client service and rename the work directory using the below commands,

service-control --stop vsphere-ui

mv /usr/lib/vmware-vsphere-ui/server/work /usr/lib/vmware-vsphere-ui/server/work_old

service-control --start vsphere-ui

And retry to login and check if you still getting unexpected error, if you still receive same error check these logs files,

/var/log/vmware/vsphere-ui/logs/vsphere_client_virgo.log

/var/log/vmware/vmware-updatemgr/vum-server/lifecycle.log

Regards

Tami

Install-Upgrade Specialist

[barnette08]

That didn't help unfortunately.

[vTara]

Could you check these logs file.

Take two putty for below commands and type those command, and then try to click on the Lifecycle manager so that you might get the unexpected error again. Now switch back to those putty session and check the logs to see if you get any clue. Try to press Ctrl+C to stop those logs flows.

tail -f /var/log/vmware/vsphere-ui/logs/vsphere_client_virgo.log

tail -f /var/log/vmware/vmware-updatemgr/vum-server/lifecycle.log

Regards

Tami

Install-Upgrade Specialist

[barnette08]

I don't really see anything helpful in those logs output.  You?

lifecycle.log

ImageManagerCTL: 18459: 2020-06-06 18:03:05,926 imagemanagerctl:976 INFO Calling with arguments: depotInfo --getcomponentinfo /storage/updatemgr/patch-store/hostupdate/__hostupdate20-consolidated-index__.xml

ImageManagerCTL: 18459: 2020-06-06 18:03:05,926 imagemanagerctl:354 INFO Get component info from depot /storage/updatemgr/patch-store/hostupdate/__hostupdate20-consolidated-index__.xml

ImageManagerCTL: 18459: 2020-06-06 18:03:05,932 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/vmw/vmw-ESXi-7.0-vmtools-11.1-metadata.zip

ImageManagerCTL: 18459: 2020-06-06 18:03:05,937 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/vmw/VMW-ESXi-7.0-IOVP-cumulative_metadata.zip

ImageManagerCTL: 18459: 2020-06-06 18:03:05,957 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/vmw/vmw-ESXi-6.5.0-metadata.zip

ImageManagerCTL: 18459: 2020-06-06 18:03:06,805 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/vmw/vmw-ESXi-6.7.0-metadata.zip

ImageManagerCTL: 18459: 2020-06-06 18:03:07,598 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/vmw/vmw-ESXi-7.0.0-metadata.zip

ImageManagerCTL: 18459: 2020-06-06 18:03:07,727 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/vmw/metadata-11.zip

ImageManagerCTL: 18459: 2020-06-06 18:03:07,755 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/DEL/DEL-ESXi-7.0-Addon-cumulative_metadata.zip

ImageManagerCTL: 18459: 2020-06-06 18:03:07,791 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/HPE/HPE-ESXi-7.0-Addon-cumulative_metadata.zip

ImageManagerCTL: 18459: 2020-06-06 18:03:07,841 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/fjt/FJT-ESXi-7.0-Addon-cumulative_metadata.zip

ImageManagerCTL: 18459: 2020-06-06 18:03:07,878 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/EMC/metadata-97.zip

ImageManagerCTL: 18459: 2020-06-06 18:03:15,391 imagemanagerctl:373 INFO Done: components' info from depot

vsphere_client_virgo.log

[2020-06-06T18:02:54.234Z] [INFO ] health-status-4               com.vmware.vise.vim.cm.healthstatus.AppServerHealthService        Memory usage: used=325,806,568; max=803,733,504; percentage=40.5366413591737%. Status: GREEN

[2020-06-06T18:02:54.234Z] [INFO ] health-status-4               c.v.v.v.cm.HealthStatusRequestHandler$HealthStatusCollectorTask   Determined health status 'GREEN' in 0 ms

[2020-06-06T18:03:08.992Z] [INFO ] agw-token-renew1             ######## ###### 200004 com.vmware.vim.sso.client.impl.SiteAffinityServiceDiscovery       Site affinity is disabled

[2020-06-06T18:03:09.092Z] [INFO ] agw-token-renew1             ######## ###### 200004 com.vmware.identity.token.impl.SamlTokenImpl                      SAML token for SubjectNameId [value=Administrator@VSPHERE.LOCAL, format=http://schemas.xmlsoap.org/claims/UPN] successfully parsed from Element

[2020-06-06T18:03:09.095Z] [INFO ] agw-token-renew1             ######## ###### 200004 com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl           Successfully renewed token for user: {Name: Administrator, Domain: VSPHERE.LOCAL}

[vTara]

Hi Barnette,

Yes I did not see any error or unusual messages in these logs. Have you ran the commands and then click on the vLCM tab to check the logs ?

Can you collect the vCenter logs and upload the zip file we will take a look at it, or open a service request.

Regards

Tami

Install-Upgrade Specialist

[barnette08]

Yes, I've done both of those actually.  Support ended up clearing the error by resetting the database and removing the patch store.  The issue though is doing that removes all uploaded components and doesn't help in root causing why this is happening to begin with .  I assume there is a bug with either vLCM or within the component itself. 

[BillFrazier]

Hi barnette08,

You can try to stop html5 client service and rename the work directory using the below commands,

service-control --stop vsphere-ui

mv /usr/lib/vmware-vsphere-ui/server/work /usr/lib/vmware-vsphere-ui/server/work_old

service-control --start vsphere-ui

The above worked for my issue. THANKS!