Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2
Fixed In:
12.0.0, 11.6.0 HF6
Opened: Jun 09, 2015 Severity: 3-Major Related Article:
K17295
GET on tm/ltm/data-group/internal/dg-name might show the following record entries - ... "records": [ ... { "name": "triple", "partition": "single", "subPath": "double", "data": "three" }, ... ] } In actuality, the identifiers of the record are not pathed, and hence the 'partition' and 'subPath' properties do not make any sense.
Misinformation in the API output. This is a cosmetic issue only. Ignore the 'partition' and 'subPath' properties.
Performing a GET operation on a device group, for example: GET tm/ltm/data-group/internal/dg-name.
None.
iControl REST: the records collection in tm/ltm/data-group/internal/ now returns the correct data for the "name" object, and no longer returns the "partition" and "subPath" objects.