Last night I had CRON set to perform the 24.10.2_8 to 25.4.x update and it didn't go, the reboot I had set for an hour later did happen so I know cron was doing it's job.
Does the 25.4 upgrade require manual intervention? I think I'll have time later today, but was hoping it would be done when I walked into work this morning.
if it matters, I generally only turn on the firmware and reboot task when I need them to run, and turn them back off the next day. I did manually run the check for updates tool yesterday to make sure I was seeing the 25.4 version listed.
Major upgrades aren't covered by the update script.
This is what you need in a cron job if scheduling is a must.
configctl firmware unlock 25.4 && configctl firmware upgrade 25.4
In case a later minor version is needed after the machine has rebooted to 25.4 - you'll need one more cron as follows.
configctl firmware update
Thanks, I was wondering if that was the case.
Cron job default is to only do minor updates for safety reasons, but you can coerce it by using the intentionally undocumented value..
https://github.com/opnsense/core/blob/7beec43db9273308e70c4c272fdcbaca0efa41bf/src/etc/rc.firmware.subr#L34
This was my first major upgrade, so I should have expected this. I'll probably keep things at default to make sure big things don't happen on their own and make a mess. That said, I am ZFS (mirror) and do create snapshots, so I'm kind of covered if something goes horribly wrong.
Ok, now you know which parameter to set in the cron job, but use it wisely :)