After upgrading vCloud Usage Meter from version 4.3/4.4 to 4.5/4.5.0.1, proxy settings get deleted from VAMI and upload to vCloud Usage Insight fails
search cancel

After upgrading vCloud Usage Meter from version 4.3/4.4 to 4.5/4.5.0.1, proxy settings get deleted from VAMI and upload to vCloud Usage Insight fails

book

Article ID: 322755

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

To be aware of the issue and learn how to fix the problem with the data upload to vCloud Usage Insight in Cloud Partner Navigator.

Symptoms:
Post upgrading Usage Meter from 4.3/4.4 to 4.5/4.5.0.1, you will notice the below symptoms:
  • Proxy settings get deleted from the VAMI page.
  • Data upload to vCloud Usage Insight in Cloud Partner Navigator fails with the following error: "Usage Insight Test Failed due to "Org.bouncycastle.tls.TlsFatalAlert : CertificateUnknown(46)".
  • Manually testing the connection between Usage Meter and Usage Insight also fails with the error above.
  • You will be able to perform the following curl operation successfully with vCloud Usage Insight:
curl -kv https://ums.cloud.vmware.com/um/api/v1/ping --proxy proxy ip address:8080
  • The Usage Meter proxy settings are lost after defining them on the VAMI page in a couple of hours or days.
  • You observe in multiple records in the logs for changing and updating the proxy configurations like the following:
2022-02-17 15:21:17.973  INFO --- [Thread-9] com.vmware.um.dss.ProxyConfigWatcher     : Got notification for proxy configuration change.
2022-02-17 15:21:17.973  INFO --- [Thread-15] c.vmware.um.umconnection.api.HttpProxy   : Updating proxy configuration file.
2022-02-17 15:21:17.974  INFO --- [Thread-16] c.vmware.um.umconnection.api.HttpProxy   : Updating proxy configuration successfully.
2022-02-17 15:21:17.974  INFO --- [Thread-12] c.vmware.um.umconnection.api.HttpProxy   : Updating proxy configuration successfully.
2022-02-17 15:21:17.974  INFO --- [Thread-13] c.vmware.um.umconnection.api.HttpProxy   : Updating proxy configuration successfully.
2022-02-17 15:21:17.974  INFO --- [Thread-18] com.vmware.um.dss.ProxyConfigWatcher     : Got notification for proxy configuration change.
2022-02-17 15:21:17.975  INFO --- [Thread-16] c.vmware.um.umconnection.api.HttpProxy   : Updating proxy configuration successfully.
2022-02-17 15:21:17.976  INFO --- [Thread-10] c.vmware.um.umconnection.api.HttpProxy   : Updating proxy configuration successfully.
2022-02-17 15:21:17.976  INFO --- [Thread-7] c.vmware.um.umconnection.api.HttpProxy   : Updating proxy configuration successfully.
2022-02-17 15:21:17.976  INFO --- [Thread-15] c.vmware.um.umconnection.api.HttpProxy   : Updating proxy configuration successfully.
2022-02-17 15:21:17.976  INFO --- [Thread-13] c.vmware.um.umconnection.api.HttpProxy   : Updating proxy configuration successfully.
2022-02-17 15:21:17.977  INFO --- [Thread-12] c.vmware.um.umconnection.api.HttpProxy   : Updating proxy configuration successfully.
2022-02-17 15:21:17.977  INFO --- [Thread-15] com.vmware.um.dss.ProxyConfigWatcher     : Got notification for proxy configuration change.
2022-02-17 15:21:17.977  INFO --- [Thread-13] com.vmware.um.dss.ProxyConfigWatcher     : Got notification for proxy configuration change.
2022-02-17 15:21:17.977  INFO --- [Thread-12] c.vmware.um.umconnection.api.HttpProxy   : Updating proxy configuration successfully.
2022-02-17 15:21:17.978  INFO --- [Thread-7] c.vmware.um.umconnection.api.HttpProxy   : Updating proxy configuration successfully.
2022-02-17 15:21:17.978  INFO --- [Thread-9] c.vmware.um.umconnection.api.HttpProxy   : Updating proxy configuration file.
2022-02-17 15:21:17.978  INFO --- [Thread-13] c.vmware.um.umconnection.api.HttpProxy   : Updating proxy configuration file.
2022-02-17 15:21:17.979  INFO --- [Thread-13] c.vmware.um.umconnection.api.HttpProxy   : Updating proxy configuration successfully.
2022-02-17 15:21:17.979  INFO --- [Thread-9] c.vmware.um.umconnection.api.HttpProxy   : Updating proxy configuration successfully.
2022-02-17 15:21:17.979  INFO --- [Thread-16] com.vmware.um.dss.ProxyConfigWatcher     : Got notification for proxy configuration change.
2022-02-17 15:21:17.979  INFO --- [Thread-12] com.vmware.um.dss.ProxyConfigWatcher     : Got notification for proxy configuration change.
2022-02-17 15:21:17.979  INFO --- [Thread-7] com.vmware.um.dss.ProxyConfigWatcher     : Got notification for proxy configuration change.
2022-02-17 15:21:17.979  INFO --- [Thread-10] com.vmware.um.dss.ProxyConfigWatcher     : Got notification for proxy configuration change.


Environment

VMware vCloud Usage Meter 4.x

Cause

Because of the multiple threads for changing and updating the proxy configuration file, the settings get lost, and the file turns corrupt.

Resolution

The VMware Engineering team is aware of the issue and working on it.

Workaround:
Procedure
  1. Take a snapshot of the Usage Meter appliance.
  2. SSH connect to the appliance as usagemeter.
  3. Navigate to opt/vmware/cloudusagemetering/conf/.
  4. Edit the nginx.conf file with the vi editor, and press I to enter into Insert mode.
vi nginx.conf
  1. Add the below entry:
jvm_options "-Dproxy_config=/tmp/vami-file";
Note: For updating the nginx.conf file, you need to switch to the root user (su -root) and supply the root password. Once the changes are made, ensure you type exit and press Enter to get back to the usagemeter account, as restarting the services with the root user will break the appliance.
  1. Stop the gateway service by navigating to /opt/vmware/cloudusagemetering.
./scripts/stop.sh GW
  1. Start the gateway service:
./scripts/start.sh GW
  1. Setup the proxy configuration on the VAMI page and save it.
Note: Ensure you set the proxy configuration with the HTTP protocol in VAMI, and HTTPS is disabled.


Additional Information

Impact/Risks:
Data upload to the vCloud Usage Insight fails, giving incorrect reports at the end of the month.

Powered by Wolken Software