Bug ID 704546: Symlinks may be corrupted by upgrade

Last Modified: Jan 29, 2019

Bug Tracker

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

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4

Opened: Jan 31, 2018
Severity: 3-Major

Symptoms

In rare cases after a software version upgrade, a corrupted symbolic link that points to a nonexistent file may exist. Processes that try to use the file will fail, often generating the message 'No such file or directory'.

Impact

A symlink is broken, but it depends on whether the symlink is necessary to BIG-IP operation as to whether a problem will be immediately apparent.

Conditions

Happens after an upgrade. This rarely encountered issue occurs when the symlink points to an absolute path (/a/b/c/d) rather than a relative one (if you are in /a/b, then the target would be c/d).

Workaround

If creating a symlink is necessary, use a relative path rather than an absolute one. If this condition is found, use the following command to rebuild the symlink: ln -fs <target> <symlink_name>

Fix Information

None

Behavior Change