Bug ID 1044249: On initial installation, blades fail to PXE boot after chassis startup

Last Modified: Jan 06, 2024

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

Fixed In:
F5OS-C 1.3.0

Opened: Sep 01, 2021

Severity: 3-Major

Symptoms

On initial installation, blades fail to PXE boot after the chassis powers on. Other symptoms: 1. When trying to deploy a tenant on a single blade or when multiple blades are bundled for the same chassis partition in the Chassis Partition webUI (TENANT MANAGEMENT > Tenant Deployments), the "Running Version" remains "Unavailable" indefinitely. 2. Blades are not available for login or other activity from the CLI.

Impact

Blades fail to PXE boot. This means they failed to load an initial image and cannot join a cluster.

Conditions

Multiple factory-fresh blades are powered up.

Workaround

On both system controllers, reboot the system controller or restart the image server container. Type this command to restart the image server on each system controller: docker restart vcc-image-server

Fix Information

N/A

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips