Hello,
A VMware engineer contacted me this morning with a working solution... I'm posting it here because this procedure is only available internally at VMware and I'm told that it is unlikely that it will be published for public consumption for some reason.
- Put your VASA provider in a state where it cannot be reached by the VCenter Appliance. In my case, I did a shutdown.
- Edit this file: /usr/lib/vmware-vpx/sps/conf/sms-config.xml and modify this section:
<!-- Retry configuration for QS connection -->
<qsConnection>
<!-- Retry attempt for QS connection. -->
<retryAttempt>99999</retryAttempt>
<!-- Retry interval (in seconds) for QS connection. -->
<retryInterval>30</retryInterval>
</qsConnection>
With:
<!-- Retry configuration for QS connection -->
<qsConnection>
<!-- Retry attempt for QS connection. -->
<retryAttempt>4</retryAttempt>
<!-- Retry interval (in seconds) for QS connection. -->
<retryInterval>30</retryInterval>
</qsConnection>
Then STOP and START the SPS service:
service-control --stop vmware-sps
service-control --start vmware-sps
Do a 'tail -f' of the SPS logs and wait until you get a 'GREEN' status that looks like this:
2018-08-02T11:23:51.010-04:00 [http-nio-127.0.0.1-22000-exec-2] DEBUG opId=sps-Main-223274-27 com.vmware.vim.storage.common.health.HealthStatusManagerImpl - Health color of the service : GREEN
- Go to your VCenter console and remove the Storage Provider
- Re-edit the above file and replace the value of '4' with the original '99999'
- STOP and START the SPS service
This procedure worked for me. I was able to re-add the Service Provider and the VVol's it contained.
I hope that this helps someone else!
