Last Modified: Dec 16, 2025
Affected Product(s):
F5OS F5OS-C, Install/Upgrade
Known Affected Versions:
F5OS-C 1.8.0, F5OS-C 1.8.1, F5OS-C 1.8.2
Opened: Nov 17, 2025 Severity: 2-Critical
A newly-installed controller running the correct software version is inaccessible from the network or peer controller, even though it is booted into F5OS. Log messages in /var/log/messages or "journalctl -u platform-services-deployment" indicating that it failed to pull docker images, and the initial registries were set as a mirror of themselves: platform-deployment: Initial registry (port 2000) setup as mirror of port 2000 registry complete platform-deployment: Initial registry (port 2500) setup as mirror of port 2500 registry complete [...] platform-deployment: Pulling repository localhost:2500/vcc-partition-software-manager platform-deployment: Error: image vcc-partition-software-manager:7.2.7-f5os-c-1-8-1-candidate.2025-02-11-05-55-35.S383ff41b not found platform-deployment: Unexpected error encountered while starting platform services via docker-compose. platform-deployment: Nov 12 11:57:57 controller-2.chassis.local platform-deployment[3342]: Error: image vcc-partition-software-manager:7.2.7-f5os-c-1-8-1-candidate.2025-02-11-05-55-35.S383ff41b not found platform-deployment: Platform services done
The VELOS system controller remains inoperative.
A fresh install of software on a VELOS system controller (an RMA replacement system controller, or a clean install via PXE or USB). During the initial boot into F5OS, the new system controller is rebooted while platform-services-deployment is still running in the background.
Perform a clean install of the VELOS system controller software again, and do not reboot the controller while platform-services-deployment is still running.
None