14.3-RELEASE-p6 to 15.0-RELEASE ipfw issues

[dkh]

I hate to say it but this upgrade has been the most painful I've seen in a lot of years. It's a big upgrade with tones of great stuff in it but the gotchas have been disappointing.

My latest adventure has been with traditional updates with freebsd-update on VPS providers Vultr and Cloudfanatic. The same result on both but I suspect the issue I saw with a physical box was the same thing and I just didn't notice it at the time.

With the physical box I had been running headless and had to get on a console to get things going again.

Same with the VPS clients. I did the initial freebsd-update update -r 15.0-RELEASE and freebsd-update install and rebooted. This locks you out of the systems. IPFW will not function in this state. You have to get on with a console and disable IPFW and reboot. That gets you a bit further. Now I've had to go into each one and replace the /usr/local/etc/pkg/repos/FreeBSD.conf file that's there (not sure where it is coming from) with a new version with the correct urls etc so that it looks like

FreeBSD-ports: {
  url: "pkg+https://pkg.FreeBSD.org/${ABI}/latest",
}
FreeBSD-ports-kmods: {
  url: "pkg+https://pkg.FreeBSD.org/${ABI}/kmods_latest_${VERSION_MINOR}",
}
FreeBSD-base: {
  enabled: no
}

At this point I could do the pkg upgrade -f, reenable IPFW in /etc/rc.conf and reboot and run the final freebsd-update install.

I don't remember the last time I've had to have access to the console to do an upgrade and I'm sure I've never had to disable the firewall to finish things up.

Anyhow, just throwing this out there on the off chance it helps someone else.

 

[T-Daemon]

Now I've had to go into each one and replace the /usr/local/etc/pkg/repos/FreeBSD.conf file that's there (not sure where it is coming from)

This is definitely a user created package repository configuration file. Such a file is neither created nor copied by the system during initial installation or during an update/upgrade process.

 

[dkh]

Completely possible, I just don't remember doing it, maybe I had thought about using basify more widely at one point.