talos: Cannot upgrade to 1.10.4
Bug Report
Cannot upgrade to Talos v1.10.4
Description
Attempting to upgrade to 1.10.4 I get the following in the console logs:
12/06/2025 11:50:47 running Talos installer v1.10.4
12/06/2025 11:50:47 system disk wipe on upgrade is not supported anymore, option ignored
12/06/2025 11:50:47 running pre-flight checks
12/06/2025 11:50:47 host Talos version: v1.10.3
12/06/2025 11:50:47 host Kubernetes versions:
12/06/2025 11:50:47 all pre-flight checks successful
12/06/2025 11:50:47 Error: failed to probe bootloader on upgrade: file does not exist
12/06/2025 11:50:47 Usage:
12/06/2025 11:50:47 installer install [flags]
12/06/2025 11:50:47
12/06/2025 11:50:47 Flags:
12/06/2025 11:50:47 -h, --help help for install
12/06/2025 11:50:47
12/06/2025 11:50:47 Global Flags:
12/06/2025 11:50:47 --arch string The target architecture (default "amd64")
12/06/2025 11:50:47 --board string Deprecated: no op (default "none")
12/06/2025 11:50:47 --bootloader Deprecated: no op (default true)
12/06/2025 11:50:47 --config string The value of talos.config
12/06/2025 11:50:47 --disk string The path to the disk to install to
12/06/2025 11:50:47 --extra-kernel-arg stringArray Extra argument to pass to the kernel
12/06/2025 11:50:47 --force Indicates that the install should forcefully format the partition
12/06/2025 11:50:47 --meta metaValueSlice A key/value pair for META (default [])
12/06/2025 11:50:47 --platform string The value of talos.platform
12/06/2025 11:50:47 --upgrade Indicates that the install is being performed by an upgrade
12/06/2025 11:50:47 --zero Indicates that the install should write zeros to the disk before installing
12/06/2025 11:50:47
12/06/2025 11:50:47 failed to probe bootloader on upgrade: file does not exist
12/06/2025 11:50:47 mmcblk0: p1 p2 p3 p4
I am starting the upgrade from Omni. Creating a new cluster where the installed version was 1.10.3 fails to also upgrade.
Logs
Omni support bundle attached.
Environment
- Talos version: [
talosctl version --nodes <problematic nodes>] Cannot provide output, no running cluster. Verions is 1.10.3 upgrade to 1.10.4 - Kubernetes version: [
kubectl version] N/A - Platform: Omni baremetal (not using provider)
About this issue
- Original URL
- State: open
- Created a year ago
- Comments: 16 (6 by maintainers)
Commits related to this issue
- fix: add more bootloader probe logs on upgrade See #11210 This doesn't fix anything, but the logs will be more helpful to understand what exactly is wrong. Signed-off-by: Andrey Smirnov <andrey.smi... — committed to smira/talos by smira a year ago
- fix: add more bootloader probe logs on upgrade See #11210 This doesn't fix anything, but the logs will be more helpful to understand what exactly is wrong. Signed-off-by: Andrey Smirnov <andrey.smi... — committed to smira/talos by smira a year ago
- fix: add more bootloader probe logs on upgrade See #11210 This doesn't fix anything, but the logs will be more helpful to understand what exactly is wrong. Signed-off-by: Andrey Smirnov <andrey.smi... — committed to smira/talos by smira a year ago
- fix: add more bootloader probe logs on upgrade See #11210 This doesn't fix anything, but the logs will be more helpful to understand what exactly is wrong. Signed-off-by: Andrey Smirnov <andrey.smi... — committed to smira/talos by smira a year ago
- fix: add more bootloader probe logs on upgrade See #11210 This doesn't fix anything, but the logs will be more helpful to understand what exactly is wrong. Signed-off-by: Andrey Smirnov <andrey.smi... — committed to smira/talos by smira a year ago
@aeleks I did use the
--stageoption before when using standalone Talos clusters; however, I am now testing clusters with Omni and have not found a way to use the stage option when upgrading.