Bug ID 913573: Unable to complete REST API PUT request for 'tm/ltm/data-group/internal' endpoint.

Last Modified: Oct 06, 2020

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS(all modules)

Known Affected Versions:
14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 16.0.0, 16.0.0.1

Opened: Jun 02, 2020
Severity: 3-Major

Symptoms

When REST API PUT request is call to modify LTM data-group internal without 'type' field in body-content, it fails intermittently with a 400 error. --{"code":400,"message":"invalid property value \"type\":\"\"","errorStack":[],"apiError":26214401} The 'type' field is not getting populated with default value and is set to null string "" instead.

Impact

Unable to update the configuration object (LTM data-group internal) with REST API PUT.

Conditions

-- PUT REST API request used to modify LTM data-group internal. -- Type field is not specified in the body-content.

Workaround

Include 'type' field inside PUT request body content for the operation to succeed. Example Curl Command: -- curl -isku <username>:<password> -H "Content-Type: application/json" -X PUT -d '{"records":[{"name":"1.1.1.1"}, {"name":"1.1.1.2"}], "type":"ip"}' https://localhost/mgmt/tm/ltm/data-group/internal/~Common~<Name>

Fix Information

None

Behavior Change