I am here trying to use VSAN Build Recommendation Engine Health thing. It asks for my.vmware.com credentials, but after providing those it fails to connect.
I think problem is that vCenter is behind a proxy and this tool is not picking up proxy setting configured on vCenter or in VSAN health plugin. I have proxy also configured on Update manager still no luck.
I know this because i was monitoring proxy log, and there is no requests coming from vCenter when i click Login.
Can someone confirm or deny, this theory? Or may be someone know how to configure proxy for this thing.
btw, also tried RVC. no luck. Here is what i got:
> vsan.login_iso_depot -u USER -p PASS
2017-08-15 16:20:37 +0000: Login to VMware ISO Depot using my.vmware.com credentials
2017-08-15 16:20:37 +0000: Note: vCenter needs to have access to depot.vmware.com.
2017-08-15 16:22:44 +0000: Failed to save cookie of depot.vmware.com.
Error: Incorrect my.vmware.com login credential.
and here is what i see in Web client:
I am running vSphere 6.5u1. vCenter Appliance with an External PSC.
Thanks in advance.
Saw your message on vE Slack.
First thing I would try is logging in directly to my.vmware.com via browser to rule out locked account or bad password... if you have not done so yet.
Are you able to download the latest version of HCL DB from vCenter using "Get latest version online" button?
In case you haven't seen this KB, here are some troubleshooting steps from KB2150914
The following issues might be detected by this check.
Thanks for the reply.
Tried all of that.
Here is what i can.
1 I can access and download latest ACL, no problem(Proxy settings in vsan config)
2. vCenter can access Vapp-Repo and check for Appliance updates.(proxy settings in VCA, and even edited proxy config file to enabled https, proxy)
3. Update manager can access and download updates(Proxy settings in update manager)
4. My my.vmware.com account is not locked, using it every day, and checked it several times.
This has to be some kind of BUG, or i am getting crazy....
Technically i could open a ticket, but this is a lab environment and i would not want to waste time of VMware support, especially if this is something simple.
Any other ideas are very welcome.
I have similar issue at the moment with vSAN 6.6.1 behind the proxy.
It might be related to a bug in the previous version of vSAN when online check of vSAN health was generating an error message as follows:
The latter is a well-known bug (no KB though) that VMware is working on to resolve.
It looks like a bug yes.
Lets hope it will be fixed soon.
Unfortunately i cannot open ticket to VMware to ask for more details, as i face this issue on one of my labs.
If anyone of you guys can open ticket, i would appreciate. It would be good to see an official statement form VMware.
Thank you for providing this link.
In a conversation with VMware GSS about a week ago, they promissed me to publish a KB about this issue. Looks like they keep their promiss. Well done!
I have just found a workable solution to this issue - https://virtualnomadblog.com/2018/02/07/vsan-6-6-1-vsan-build-recommendation-engine-health-issue-res... .
It would be great if you could test it as well and let me know.
Interesting case. What is the version of VCSA you're running on? I was able to resolve all issues only after updating to 6.5 U1e.
Also, can you check the following:
If all those settings are fine, please reboot the appliance and chech the status of vSAN Build Recommendation Engine Health.