Upgrade from 17.1.9 to 17.7.r1?

[RickNY]

Is there a way to upgrade from 17.1.9 to 17.7.r1 from the command line in a stable way that will not mess up upgrading to the released 17.7 when it comes out?

Thanks
Rick

[franco]

Hi Rick,

It's complicated. The short answer is no but it's for staging reasons. When 17.1 is EoL you will be able to upgrade seamlessly, the upgrade from the GUI will also be supported this time. Until then we want to move the last pieces into place, allowing upgrades of development packages. There are also new signing keys which prevent the current 17.1.x from working flawlessly due to precaution...

17.1.10's development package will have update code + signing info to go to 17.7-RC1's development package (which is mostly the same as 17.7-RC1 but kept separate to be able to stay on the development track). Theoretically, you could go to 17.7-RCX by doing:

# opnsense-update -t opnsense-devel

(Upgrade from the GUI or console option 12)

# opnsense-update -t opnsense

Note the above only works when 17.1.10 has been released early next week. There may be an 17.7-RC2 just to smooth things out, either online-only or with images (if we want to test the installers again). We are not 100% sure yet.

17.1.11 should be EoL, there will be a Hotfix like 17.1.11_1 to allow the upgrade to 17.7. The release date for 17.7 is July 31.

We don't encourage upgrading 17.1 to 17.7 just yet, but given the right precautions (like snapshots in a VM) and screening the release notes for known issues and how to fix them there's no reason not to try.

I hope that helps. If not, happy to discuss this in more detail.


Cheers,
Franco

[nmiller0113]

Quick question then. If I'm running the 17.7 release candidate will I need to do anything when the stable production release comes out in order to move to that from the release candidate?  Thanks!

[franco]

No, no manual steps necessary at all. 17.7-RCX will upgrade to 17.7 and subsequently 17.7.x so you are already on the next stable track.


Cheers,
Franco

[the_wolf]

I try to update but appears this error.:

***GOT REQUEST TO UPGRADE: maj***
Fetching packages-17.7.r1-LibreSSL-amd64.tar: .....opnsense-verify: Unable to open /var/cache/opnsense-update/40360/packages-17.7.r1-LibreSSL-amd64.tar: No such file or directory
 failed
***DONE***

[franco]

Hi there,

See last bit of https://forum.opnsense.org/index.php?topic=5494.0 -- LibreSSL is not supported during pre-releases.

You can change to OpenSSL, then the upgrade will go through as expected and switch back next week when 17.7's LibreSSL repository is uploaded.


Cheers,
Franco

[the_wolf]

thank you

[the_wolf]

is already the fourth time that I update, it restarts automatically and I'm going in for updates and asks again.

[franco]

The screenshot you posted looks ok. Note you are on the development version, so when you upgrade, the upgrade code will still be active for testing reasons. You'll see from the dashboard if you made it to the new version, and you can "Check for updates" to update to 17.7.r2 (it'll be in the list).

[RickNY]

So, after doing a couple of command-line updates, I now find myself with the lobby showing "OPNsense 17.7.r_54-amd64" as of now.  Is that 17.7.r2?

[the_wolf]

Yes it happens anyway. Ai update the packages and restart and you're done. I don't need to do anything else???

[franco]

When you are there, go back to the release:

# opnsense-update -t opnsense

then the dashboard should show version 17.7.r1, the upgrade box should be gone and updates for 17.7.r2 should be visible.


Cheers,
Franco

[RickNY]

OK.. I think Im where I should be now..

[franco]

Looks good indeed.

There is a fix you should apply to r2, it has trouble upgrading from the GUI in some instances:

https://github.com/opnsense/core/commit/f0c8e2f9

Applies with:

# opnsense-patch f0c8e2f9


Cheers,
Franco

[the_wolf]

Now this 100%. Doing this the wrong way. Sorry. Thank you very much.