Bug ID 2149173: UEFI flag on GCP-based BIG-IP instances causes upgrade failure and boot loop to same volume

Last Modified: Feb 03, 2026

Affected Product(s):
BIG-IP Install/Upgrade, TMOS(all modules)

Known Affected Versions:
17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2, 17.1.3, 17.1.3.1

Opened: Nov 07, 2025

Severity: 3-Major

Symptoms

Upgrade completes but device reboots into the same old volume. Below logs can be observed. Console Logs: UEFI: Failed to load image. Description: UEFI Google PersistentDisk FilePath: PciRoot(0x0)/Pci(0x3,0x0)/Scsi(0x1,0x0) OptionNumber: 1. Status: Not Found BdsDxe: failed to load Boot0001 "UEFI Google PersistentDisk " from PciRoot(0x0)/Pci(0x3,0x0)/Scsi(0x1,0x0): Not Found SeaBIOS (version 1.8.2-google) Machine UUID ecaa9b4b-38a4-e592-a96d-3300ae1f401b found virtio-scsi at 0:3 virtio-scsi vendor='Google' product='PersistentDisk' rev='1' type=0 removable=0 virtio-scsi blksize=512 sectors=419430400 = 204800 MiB drive 0x000f3ae0: PCHS=0/0/0 translation=lba LCHS=1024/255/63 s=419430400 Sending Seabios boot VM event.

Impact

Pre-17.5.0 UEFI-enabled GCP images cannot boot into upgraded versions, causing upgrade failures.

Conditions

- A pre-17.5.0 GCP image with 2 boot locations is in use. - The UEFI_COMPATIBLE flag is set on the image. - TMOS is installed into the second boot location

Workaround

Deploy another instance of BIG-IP VE using the correct image for the desired target TMOS software version. The original configuration can then be restored from UCS backup. To avoid facing the same issue on future upgrades, only set the UEFI_COMPATIBLE flag on the image if it is currently running TMOS v17.5.0 or higher.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips