Edit Kubernetes configuration from UI and API fail with Internal Server Error (i.e. Status code 500) on TCA-CP
search cancel

Edit Kubernetes configuration from UI and API fail with Internal Server Error (i.e. Status code 500) on TCA-CP

book

Article ID: 325382

calendar_today

Updated On:

Products

VMware VMware Telco Cloud Automation

Issue/Introduction

To provide a workaround in case customer faces failures during edit Kubernetes configuration on TCA-CP.

Symptoms:
When customer is editing existing Kubernetes configuration from UI or API , it will fail throwing "Http failure response" with status code 500.

Environment

VMware Telco Cloud Automation 2.1

Cause

For existing Kubernetes configuration data "Type" information missing and edit operation needs "Type" information for validation.

Resolution

VMware is aware of this issue and working to fix it in a future release of Telco Cloud Automation 2.2.0

Workaround:

Update the patch_war_script.sh war file on TCA-CP

1. SSH to the TCA-CP as admin
2. Move to /opt/vmware directory

cd /opt/vmware

3. Download the attached binary (i.e. edit_config_patch.tar.gz ) to current folder (i.e. /opt/vmware)
4. Extract tar.gz file in current folder and run patch_war_script.sh

tar -xvf edit_config_patch.tar.gz
./patch_war_script.sh

5. Verify Edit operation from the TCA UI.



Attachments

edit_config_patch.tar get_app