vCloud Director 10 unable to register with Usage Meter 3.6.1 HP3

-
I had a issue registering vCloud director 10 with Usage Meter 3.6.1 HP3
Error : Service Unavailable







  •  Checked on the compatibility guide the versions  is supported
  • Port 443 is open even (customer had a firewall between them but firewall doesn’t seems to be a issues)



Found out there is know issue with vCloud director v10. If you disable the provider access to the legacy API login endpoint, all API integrations that rely on the system administrator login stop working, including vCloud Usage Meter and vCloud Availability for vCloud Director

Workaround:


  • Re-enable the service provider access to the legacy /api/sessions  endpoint by using the cell management tool.
  • To enable the provider access to the /api/sessions API endpoint, run the following command on the vCloud Direcotor
  • /opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n vcloud.api.legacy.nonprovideronly -v false


Below are some documentation for your perusal

https://docs.vmware.com/en/vCloud-Director/10.0/rn/VMware-vCloud-Director-for-Service-Providers-100-Release-Notes.html#knownissues    -->    vCloud Director 10.0 for Service Providers Release Notes

https://docs.vmware.com/en/vCloud-Director/10.0/com.vmware.vcloud.install.doc/GUID-84390C8F-E8C5-4137-A1A5-53EC27FE0024.html   -> Disable the Service Provider Access to the Legacy API Endpoint

Comments

Post a Comment

Popular posts from this blog

VAPI Endpoint service failure

-
VAPI Endpoint service failure  ERROR | state-manager1            | StsBuilder                     | Failed to acquire token for the solution user 2018-11-15T21:50:42.647Z | ERROR | state-manager1            | DefaultStateManager            | Could not initialize endpoint runtime state. com.vmware.vapi.endpoint.config.ConfigurationException: com.vmware.vim.sso.client.exception.AuthenticationFailedException: Provided credentials are not valid.         at com.vmware.vapi.endpoint.cis.StsBuilder.createToken(StsBuilder.java:182)         at com.vmware.vapi.endpoint.cis.StsBuilder.rebuild(StsBuilder.java:77)      ...
Read more

Replacing vROPS Certificates

-
Image
Issue:  When using default certificates in vROPS  Due to security requirements it was necessary to replace the default self-signed certificates with a trusted certificate signed by an internal CA. Unlike vCenter, vROPS uses a common name vc-ops-slice-1 followed by slice-2 for data and other node, where vCenter has SAN names in the default certificate so when you add the root of the local machine trusted store then the vCenter url shows secured. In order to make the secure SSL we have to generate the CSR and get it signed by any third party SSL vendors or our own Microsoft CA.  I will be generating a CSR and getting signed by internal Microsoft CA .We can refer this below article from VMware as reference.  https://kb.vmware.com/s/article/2046591?lang=en_us Steps:  1.The first step is to create a new private key from taking a SSH session to master node vROPS. openssl genrsa -out vrops.key 2048 2. Using the configuration file below make sure to provide de...
Read more

vPostgres service fails to start with Fatal error : bogus postmaster.pid

-
I came across this issue today where vPostgres service was failing on VCSA with error Fatal Error. # service-control --start vmware-vpostgres Perform start operation. vmon_profile=None, svc_names=['vmware-vpostgres'], include_coreossvcs=False, include_leafossvcs=False 2019-11-06T21:38:14.283Z   Service vmware-vpostgres state STOPPED Error executing start on service vmware-vpostgres. Details {     "resolution": null,     "detail": [         {             "args": [                 "vmware-vpostgres"             ],             "id": "install.ciscommon.service.failstart",             "localized": " A...
Read more