Last Modified: Oct 19, 2025
Affected Product(s):
F5OS Install/Upgrade, Velos
Known Affected Versions:
F5OS-C 1.5.1, F5OS-C 1.8.0, F5OS-C 1.8.1, F5OS-C 1.8.2
Opened: May 18, 2023 Severity: 3-Major
Blades may fail to join the openshift cluster if local docker images have been corrupted. This is indicated by the blade failing to cluster and messages similar to following in the /var/log/openshift.log file. 2023-05-04 03:55:20.563625 - fatal: [blade-3.chassis.local]: FAILED! => {"attempts": 10, "changed": false, "cmd": ["atomic", "pull", "--storage=ostree", "docker:controller-ha.chassis.local:2000/openshift-3.11/ci-cd/496e03f/openshift/origin-node:3.11.0.496e03f"], "delta": "0:00:14.337307", "end": "2023-05-04 03:55:20.470795", "msg": "non-zero return code", "rc": 1, "start": "2023-05-04 03:55:06.133488", "stderr": "time=\"2023-05-04T03:55:20Z\" level=fatal msg=\"Error initializing source docker-daemon:controller-ha.chassis.local:2000/openshift-3.11/ci-cd/496e03f/openshift/origin-node:3.11.0.496e03f: Error loading image from docker engine: Error response from daemon: file integrity checksum failed for \\\"usr/bin/openshift\\\"\"", "stderr_lines": ["time=\"2023-05-04T03:55:20Z\" level=fatal msg=\"Error initializing source docker-daemon:controller-ha.chassis.local:2000/openshift-3.11/ci-cd/496e03f/openshift/origin-node:3.11.0.496e03f: Error loading image from docker engine: Error response from daemon: file integrity checksum failed for \\\"usr/bin/openshift\\\"\""], "stdout": "", "stdout_lines": []}
Blades affected will not be able to join the openshift cluster , and will not be able to deploy tenants.
A single of instance of this issue has been seen after an upgrade of a new chassis from 1.2.1 to 1.5.1.
PXE booting the blades, will install fresh images on the blade, and they will then be able to join the openshift cluster.
None