Upgrading from 19.7.10 to 20.1

[JoK]

Sorry if this is a stupid question, but if I try to update my 19.7.10 in the OPNsense software, hitting the "check for updates" there is no updates available, but I can see that 20.1 is out now?

Is it not possible to update via update in OPNSense with this version?

[iam]

Remember that when 20.1 is available it will take up to a day before we release the hotfix with the major upgrade path enabled. Please be patient as we simply want to ensure that upgrades will not be bumpy affair.

[franco]

iam <3

It will probably take just a one or two more hours. We would like to test so you don't have to. ;)


Cheers,
Franco

[Pocket_Sevens]

Is it recommended to do a fresh install of 20.1 (and restore our settings) or will the update via GUI be fine?

[iam]

Update via GUI should be fine. I've just updated a PCEngines APU and a APU2 and haven't observed any issues so far. Contrariwise on the APU2 I reach the full download speed (300Mbit/s, PPPoE) now although the upgrade to HardenedBSD 12.1 was skipped  :)

[eprom]

for i386 version everything is fine, updated from console.
Thank opnsense team for smooth upgrade.

[madj42]

I feel stupid asking this question.  For those that upgraded, are you switching to development or leaving it as production in the settings?  I'm not seeing the upgrade unless I switch to development.

Update: I figured it out.

[tong2x]

mine is downloading to long, based on the download graph not much is being downloaded...
or maybe the download is slow since everyone is downloading...

its been running for more than 2 hours downloading...

[szty0pa]

I am having probably the same issue as @tong2x: upgrading a 4GB storage system in-place from the web GUI is not possible as it fills up the whole storage (about 110% in my case) and then freaks out. (It was working for the major upgrades before.)
I am trying to investigate this issue further, will get back if I found something.

--update--
CLI manual upgrade with

Code Select Expand

opnsense-update -sn "20.1\/latest" works as intended.

[meazz1]

I fresh installed 20.1 on my pc. I downloaded the img from the download page.
I'm new Opnsense and have a question, what is a "Production Series"? Is this not meant for regular home users?

I looked but could not find the answer.

[franco]

--update--
CLI manual upgrade with

Code Select Expand

opnsense-update -sn "20.1\/latest" works as intended.

This will break on major upgrades that require a new kernel and base system that is incompatible with older version. You don't have enough space to upgrade. The sanest approach is to abort until enough free space has been made available.

meazz1: "production" means ready for production environments and our older versions are out of support / have no more updates.


Cheers,
Franco

[chemlud]

"Production series" is meant to be stable enough to be used under production conditions. The nightly builts are experimental... ;-)

[JoK]

Thanks guys, I just updated to 20.1 and it went smooth :-)

[tokade]

Upgraded my installation without any problems so far.

Thx guys for your great work!

[szty0pa]

This will break on major upgrades that require a new kernel and base system that is incompatible with older version. You don't have enough space to upgrade. The sanest approach is to abort until enough free space has been made available.

Hi Franco,

Sadly on a 4GB system I am roughly 62% full constantly (OPNSense takes up 1.9GB of the usable 3.4GB), that does not really change over time (I have /tmp and /var as ramdisks).
During this update something went sideways for me from the GUI: the files in /root/var/cache/opnsense-update took up roughly 1.2GB according to 'du -chP'! (Which was all the space I had then.) I used the RageNetwork mirror to update on two separate instances simultaneously, they both run into the same wall. (Checking out the mirror now I see the kernel+base+packages sets should not have taken up more than 670ish MB! Could it have been a download issue the files not receiving an EOF and curl/wget not checking/enforcing file sizes?)

Would that be a viable option for systems with smaller storage to only update the kernel and base in the first round, and only then the packages using 'pkg update' instead of extracting them from the 560ish MB packages-*.tar archive to mitigate storage limitation?

Previous major upgrades went smoothly for me on these boxes for the last ~three years, and as I see the kernel+base+packages sets size was mostly the same, I was using a different mirror though(!), so that might have been the issue this time, and everything is working as intended.


UPDATE:

I tried to revert and update again one of the firewalls. This time it went smoothly using the Dutch OPNSense mirror. So the issue might have been a one off download error, anyway I will be using the official Dutch mirror from now on.