Solved No updates needed to update system

[jbo@]

I'm preparing a couple of servers for updating from 13.0-RELEASE to 13.1-RELEASE.

I have a "test" system running 13.0-RELEASE-p6:

jbo@hq:~ % uname -a
FreeBSD hq 13.0-RELEASE-p6 FreeBSD 13.0-RELEASE-p6 #0: Mon Jan 10 06:28:50 UTC 2022     root@amd64-builder.daemonology.net:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64

I wanted to update this from p6 to p11 before updating to 13.1-RELEASE. Here's what happened:

jbo@hq:~ % sudo freebsd-update fetch
src component not installed, skipped
Looking up update.FreeBSD.org mirrors... 2 mirrors found.
Fetching metadata signature for 13.0-RELEASE from update2.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.

No updates needed to update system to 13.0-RELEASE-p11.

WARNING: FreeBSD 13.0-RELEASE-p6 is approaching its End-of-Life date.
It is strongly recommended that you upgrade to a newer
release within the next 2 months.


jbo@hq:~ % sudo freebsd-update install
src component not installed, skipped
No updates are available to install.
Run '/usr/sbin/freebsd-update fetch' first.

What's up with that? There are no updates to update from p6 to p11?

 

[Cath O'Deray]

rm -r /var/db/freebsd-update/*

Postscript: maybe not, please see below.

 

[SirDice]

What's up with that? There are no updates to update from p6 to p11?

What does freebsd-version -uk say? Have you rebooted yet?

 

[Cath O'Deray]

… Have you rebooted yet?

I may be mistaken, but I vaguely recall that in the absence of a timely restart, the fetch will trigger something other than what's in the opening post. Let's check …

---

… probably ignore me, I was thinking of <https://forums.freebsd.org/attachments/11683/>, which is subtly different.

 

[SirDice]

If you already did the whole fetch/install thing but haven't rebooted yet the 'running' kernel (shown with uname -a) will show the 'old' version. freebsd-version -uk however will show the 'new' version. Running fetch/install again won't do anything, because everything's already been done. You just need to reboot to load the new kernel.

 

[jbo@]

Fair enough... Seems like a reboot was indeed the missing action.
I checked my notes for that particular system and they don't reflect that I ran an update without rebooting prior. But I guess it's definitely most likely a screw-up on my end.

Now to wait for poudriere to finish doing its thing

Thanks!