Bug ID 1117561: Vcc-terminal-server gets stuck in unsuccessful restart loop

Last Modified: May 29, 2024

Affected Product(s):
F5OS Velos(all modules)

Fixed In:
F5OS-C 1.5.0

Opened: Jun 21, 2022

Severity: 3-Major

Symptoms

Terminal services will fail to function and the vcc-terminal-server-main component container will appear to be stuck with a status of restarting.

Impact

This should generally not be seen in normal usage, although error conditions can trigger a basic container reset.

Conditions

When the vcc-terminal-server-main component container is restarted without first recreating the container from scratch, internal filesystem changes persist which prevent it from starting up successfully.

Workaround

Restarting the system should perform a complete bringup of all component containers, including vcc-terminal-server-main, resulting in normal operation.

Fix Information

This fix modifies the internal filesystem operations such that they do not prevent the container from initializing properly after a basic restart.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips