I can reproduce the `systemctl` argument parsing issue on a standard Raspberry Pi 4 Model B Rev 1.4, running Ubuntu 26.04.1 LTS (arm64).
Environment: - `piboot-try`: 1.1ubuntu0.1 - `systemd`: 259.9-0ubuntu0.1 The command: ```console $ systemctl --dry-run reboot "0 tryboot" Too many arguments. ``` Initially, after upgrading and rebooting, I received the message that the new boot assets had failed and that Ubuntu had fallen back to the known-good state. The running kernel was `6.8.0-1065-raspi`, `/boot/firmware/new/state` contained `bad`, and the journal reported: ```text Marked new boot assets bad ``` However, after running `piboot-try --reset-new` and retrying, the Pi successfully booted kernel `7.0.0-1020-raspi`. The validation service subsequently reported: ```text Switched new boot assets to current successfully ``` The new boot assets are now in `current/`, with state `good`, and the previous boot assets have been retained in `old/`, also with state `good`. So I can reproduce the systemd argument parsing error on a Raspberry Pi 4B, but I have **not** reproduced the persistent trial-boot failure described in the report. After resetting and retrying, the new kernel booted and was successfully validated on my hardware. I hope this additional result helps distinguish the reboot-argument issue from the second boot-slot issue described here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2167775 Title: Ubuntu 26.04 on Raspberry Pi CM4: A/B kernel updates never apply To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/piboot-try/+bug/2167775/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
