Owut upgrade took too long

root@fmp:~# apk --update-cache add owut
(1/2) Installing ucode-mod-uclient (2025.10.03~dc909ca7-r2)
Executing ucode-mod-uclient-2025.10.03~dc909ca7-r2.post-install
(2/2) Installing owut (2026.01.13~2526d84b-r1)
Executing owut-2026.01.13~2526d84b-r1.post-install

  • Please see owut section of /etc/config/attendedsysupgrade for example options.
    OK: 35.0 MiB in 222 packages
    root@fmp:~# owut upgrade
    ASU-Server https://sysupgrade.openwrt.org
    Upstream https://downloads.openwrt.org
    Target x86/64
    Profile generic
    Package-arch x86_64
    Version-from 25.12.0-rc3 r32486-30527a4c34 (kernel 6.12.66)
    Version-to 25.12.0-rc4 r32534-12374d88b9 (kernel 6.12.66)
    29 packages are out-of-date
    There are 0 missing and 1 modified default packages
    Request hash:
    d7591f51675236ef7f233079190c5dbfbc6817a0b44ab1987fbb8875fb40c5a5
    --
    Status: queued - 3062 ahead of you
    Progress: 487s total = 487s in queue + 0s in build

There are 3+k queued requests waiting already, why are you surprised?

The OpenWrt ASU server is currently broken. You can use an alternate server, say https://sysupgrade.guerra24.net, until https://sysupgrade.openwrt.org is restarted.

This will use the guerra24 server until you reboot, at which point it will reset to the openwrt one (there's no uci commit, so the server change not persistent).

uci set attendedsysupgrade.server.url="https://sysupgrade.guerra24.net"
owut upgrade ...
4 Likes

ERROR: Build failed with status 502 (--version-to 25.12.0-rc4 --device x86/64:generic:ext4)
The above errors are often due to the upgrade server lagging behind the
build server, first suggestion is to wait a while and try again.

Just like last time you tried to upgrade to an unannounced release. RC4 isn't out, have fun banging your head against the wall, again.

2 Likes