Bug ID 983021: Tmsh does not correctly handle the app-service for data-group records

Last Modified: Jan 20, 2023

Bug Tracker

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

Known Affected Versions:
14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,,,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6,, 15.1.7, 15.1.8,, 16.0.0,, 16.0.1,,, 16.1.0, 16.1.1, 16.1.2,,, 16.1.3,,,

Opened: Jan 15, 2021
Severity: 4-Minor


-- The guishell shows the app_id as the default application for the folder /Common/example_app.app and not what was specified, which was 'none'. -- If the record has an app_id configured, the output of tmsh list data-group should list the app-service.


-- Unable to properly manage the lifecycle of data-group records created via an iApp. -- Unable to update data-group records at all via iControl REST, because the entire set of records must be managed altogether, and strict-updates prevents the existing records from being modified. -- Inconsistent behavior across a save-and-load operation. (The app-service is not serialized to the configuration, so after save and load, the app-service is dropped from the data-group records.)


Create an application service using tmsh.


After every iApp template deploy/update, run the following command: tmsh save sys config && tmsh load sys config

Fix Information


Behavior Change