Save to additional cost driver fails

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

Saving in additional cost driver fails after saving couple of entries.

Environment

Aria Operations 8.18.x

VCF Operations 9.0

Cause

The request from UI fails due to payload size limits

Resolution

Workaround to create additional cost drivers through Suite-api

Use suite-api to create additional cost drivers. There are no payload size limits through the suite-api route.

Use this API with POST /internal/costdrivers/additional for additional cost driver creation.
To retrieve the existing additional cost configs use GET /internal/costdrivers/additional

NOTE: When using the suite-api POST route to create new additional cost configs, all the existing configs have to be provided in the payload along with the new config to be added. This should be done to prevent overwriting of the older configs with the new config.

Workaround to create additional cost drivers through UI

1. SSH to each node
2. Open the file /usr/lib/vmware-vcops/tomcat-web-app/webapps/ui/WEB-INF/classes/struts.xml in edit mode.
3. vi /usr/lib/vmware-vcops/tomcat-web-app/webapps/ui/WEB-INF/classes/struts.xml
4. At line 6 of the file, modify the struts.multipart.maxStringLength value to preferably double the existing size.
5. Modify <constant name="struts.multipart.maxStringLength" value="16384"/> to <constant name="struts.multipart.maxStringLength" value="32678"/> in all the nodes
6. Save and close the above file
7. Restart the UI service in all the nodes systemctl restart vmware-vcops-web.service
8. Try to edit from UI and it should work fine.