Error: Http failure response for https://#.#.#.#/ets/orgs/default/direct/v271/vnflcm/v2/vnf_instances/<uuid>/heal: 400 OK
searchcancel
Error: Http failure response for https://#.#.#.#/ets/orgs/default/direct/v271/vnflcm/v2/vnf_instances/<uuid>/heal: 400 OK
book
Article ID: 367379
calendar_today
Updated On: 05-06-2025
Products
VMware Telco Cloud Automation
Issue/Introduction
CaaS and NF LCM operations fail with error: Http failure response for https://#.#.#.#/ets/orgs/default/direct/v271/vnflcm/v2/vnf_instances/########.#####.#####.#####.#########/heal: 400 OK
Environment
TCA 3.0 and 3.1
Google Chrome 124.x
Mozilla Firefox 126
Cause
Browsers have begun attaching an HTTP Priority header to all API requests made from the browser, for all websites.
This new header conflicts with our Priority header, which TCA uses or advanced prioritization operations via the API.
The NF / CaaS LCM operations fail due to the unexpected value being received in the header of the API call.
Resolution
Resolved in TCA 3.1.1 by deprecating the priority header in favor of a new x-tca-priority header.
TCA 2.2 / 2.3
Perform the following steps on every TCA Manager appliance:
SSH to the TCA-Manager appliance via admin user.
Switch to root user by running the command: su
Edit the file /opt/vmware/config/apache-httpd/hcx-virtual-hosts.conf vi /opt/vmware/config/apache-httpd/hcx-virtual-hosts.conf
Add the following line within the VirtualHost section (ensure indentation is correctly maintained): RequestHeader unset Priority
Restart the apache-httpd service systemctl restart apache-httpd
You can now perform operations on VMware Telco Cloud Automation as usual.
NOTE: The Advanced Prioritization request via APIs will no longer be honored after this change
TCA 3.0 / 3.1
SSH into the TCA Manager appliance using the adminuser.
Copy the following command to apply the patch configuration. (Or you can download, copy, and paste the contents of the TCA-3x-400Error-367379_Patch.txt attachment)
kubectl apply -f - <<EOF
apiVersion: networking.istio.io/v1alpha3
kind: EnvoyFilter
metadata:
name: tca-priority-header-fix
namespace: tca-mgr
spec:
configPatches:
- applyTo: HTTP_FILTER
match:
context: GATEWAY
listener:
filterChain:
filter:
name: envoy.filters.network.http_connection_manager
subFilter:
name: envoy.filters.http.router
patch:
operation: INSERT_BEFORE
value:
name: envoy.lua
typed_config:
'@type': type.googleapis.com/envoy.extensions.filters.http.lua.v3.Lua
inlineCode: |
function envoy_on_request(request_handle)
local priorityHeader = request_handle:headers():get("Priority")
if not (priorityHeader == nil) and priorityHeader:find("%D") then
request_handle:headers():remove("Priority")
end
end
EOF
Proceed to continue working on any NF / CaaS LCM operations.
Additional Information
Note:
This affects only the TCA-Manager appliance. TCA-CP appliances are not affected.
Google Chrome version 123 and below will not exhibit this problem.