Hi, just a quick update.
I opened a SR last Jan 25. but the Support Engineer Team haven't provided a real solution yet.
They said that the message has been resolved in VMware ESXi, 7.0.3, Build Number20842708 (we already have it). So the first advice was to silence the warning in vCenter and check if it appears again. It didn't reappear in vSAN Skyline Health but the file /storage/log/vmware/vsan-health/vmware-vsan-health-service.log on the vcsa repeatedly logged some warnings:
2023-01-25T07:29:40.338Z WARNING vsan-mgmt[11833] [VsanVumCoreUtil::CheckVumServiceStatus opID=noOpId] Failed to connect VUM service: no element found: line 1, column 0
2023-01-25T07:29:40.342Z WARNING vsan-mgmt[11833] [VsanVumCoreUtil::CheckVumServiceStatus opID=noOpId] Failed to connect VUM service: no element found: line 1, column 0
2023-01-25T07:29:40.342Z INFO vsan-mgmt[11833] [VsanVumIntegration::VumStatusCallback opID=noOpId] VUM is not installed or not responsive
Then they said the issue could be that the skyline health service should not use the proxy for internal communication. I was asked to
1. Log onto the vcsa and change the following
/etc/sysconfig/proxy the NO_PROXY line to:
NO_PROXY="localhost, 127.0.0.1, myvcentername.mydomain.mysuffix"
2. Restart the vcsa
3. Run the following and send the output
curl --noproxy '*' -v http://$(/usr/lib/vmware-vmafd/bin/vmafd-cli get-pnid --server-name localhost):9084/vci/downloads/health.xml
Output (after vcsa reboot)
# curl --noproxy '*' -v http://$(/usr/lib/vmware-vmafd/bin/vmafd-cli get-pnid --server-name localhost):9084/vci/downloads/health.xml
* Trying 127.0.0.1:9084...
* Connected to <myvcentername.mydomain.mysuffix> (127.0.0.1) port 9084 (#0)
> GET /vci/downloads/health.xml HTTP/1.1
> Host: <myvcentername.mydomain.mysuffix>:9084
> User-Agent: curl/7.83.1
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< date: Tue, 07 Feb 2023 16:40:20 GMT
< last-modified: Tue, 07 Feb 2023 14:14:13 GMT
< content-type: application/xml
< accept-ranges: bytes
< cache-control: max-age=3600,public
< content-length: 431
< x-envoy-upstream-service-time: 1
< server: envoy
<
<?xml version="1.0" encoding="UTF-8"?>
<vimhealth schemaVersion="1.0" xmlns="http://www.vmware.com/vi/healthservice" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<health id="com.vmware.vcIntegrity">
<name>VMware Update Manager</name>
<status>green</status>
<health id="com.vmware.vcIntegrity.vum">
<name>VMware Update Manager</name>
<status>green</status>
</health>
</health>
</vimhealth>
* Connection #0 to host <myvcentername.mydomain.mysuffix> left intact
After vcsa restart, events in the log are different: approximately every hour some messages are repeatedly recorded in the /storage/log/vmware/vsan-health/vmware-vsan-health-service.log file:
2023-02-08T12:28:09.474Z WARNING vsan-mgmt[08802] [VsanPhoneHomeWrapperImpl::_try_connect opID=noOpId] Cannot connect to VUM. Will retry connection
2023-02-08T12:28:09.493Z WARNING vsan-mgmt[08803] [VsanPhoneHomeWrapperImpl::_try_connect opID=noOpId] Cannot connect to VUM. Will retry connection
2023-02-08T12:28:26.502Z INFO vsan-mgmt[10191] [VsanVumIntegration::VumStatusCallback opID=noOpId] VUM is installed and connected
In the end I was asked to collect logs and they have submitted a PR (Problem Report) with their internal engineering.
We are waiting for further updates!
