Bug ID 755197: UCS creation might fail during frequent config save transactions

Last Modified: May 29, 2024

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1

Fixed In:
16.0.0, 15.1.2,,

Opened: Jan 10, 2019

Severity: 3-Major


If 'tmsh save sys config' is run simultaneously with 'tmsh save sys ucs <file>', there is the possibility of a race condition where a file gets scheduled to be added to the UCS file, but gets deleted by the save-config before it actually gets saved.


The UCS is not created, and system posts messages similar to the following: -- config/bigip_base.conf/: Cannot stat: No such file or directory. -- Exiting with failure status due to previous errors. -- Operation aborted. This is a rare, timing-related occurrence. Even though the 'save sys ucs <file>' aborts and logs errors, simply re-running the command is likely to succeed.


-- Run 'save sys config' at the same time as 'save sys ucs <file>' in tmsh. -- Files are getting added by one tmsh command, yet deleted by the other. For example, when deleting a file that has not been saved to the configuration, while the system tried to create a UCS that contains that to-be-deleted file. Note: There are many operations in which 'save sys config' is performed internally, so running the 'save sys ucs <file>' operation might encounter the timing error any time, even when you are not manually running 'save sys config'.


Re-run the 'save sys ucs <file>' after it aborts. Nothing else needs to be changed or restored.

Fix Information

The race condition is avoided and the 'save sys ucs <file>' now succeeds due to files removed by 'save sys config'.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips