Last Modified: Oct 19, 2025
Affected Product(s):
F5OS Velos
Known Affected Versions:
F5OS-A 1.1.0
Fixed In:
F5OS-A 1.3.0, F5OS-A 1.2.0, F5OS-A 1.1.1
Opened: Jun 14, 2022 Severity: 2-Critical
When the system hostname is changed and the system is rebooted, all or some of the following symptoms may be encountered: -- System-related pods in K3s are stuck in a failure state. -- The K3s cluster shows more than one node. -- OMD continuously cores.
-- K3s cluster goes into an unhealthy state. -- Tenant functionality is impacted.
The system is rebooted after the hostname is configured in confd.
None
Changing the hostname via confd does not change the system hostname. Configured hostname is reflected only in the bash and confd prompts. When no hostname is configured, the bash prompt uses a default PS1 prompt.