21.7 Rollback to 21.1

Started by lilsense, July 28, 2021, 06:00:05 PM

Previous topic - Next topic
Hi is there a way to rollback the OPNSense if things don't work out?

If not: Should this option be implemented in the 22+?

Save your config, upgrade, if its borked, re-install 21.1 and upload your config...

Quote from: lilsense on July 28, 2021, 06:00:05 PM
Hi is there a way to rollback the OPNSense if things don't work out?

If not: Should this option be implemented in the 22+?

If you don't have extra repos enabled the update should go smooth. To be on the safe side: download OPNsense for your system and make a backup of your config before you update via GUI or console...
kind regards
chemlud
____
"The price of reliability is the pursuit of the utmost simplicity."
C.A.R. Hoare

felix eichhorns premium katzenfutter mit der extraportion energie

A router is not a switch - A router is not a switch - A router is not a switch - A rou....

not what I am asking and I am aware of reinstalling OS.

What I am asking is having a feature to have a partition to restore just like a juniper switch running a Freebsd.

Maybe have a look at the documentation

https://docs.opnsense.org/manual/opnsense_tools.html
kind regards
chemlud
____
"The price of reliability is the pursuit of the utmost simplicity."
C.A.R. Hoare

felix eichhorns premium katzenfutter mit der extraportion energie

A router is not a switch - A router is not a switch - A router is not a switch - A rou....

July 28, 2021, 07:43:09 PM #5 Last Edit: July 28, 2021, 07:45:34 PM by lilsense
that may not solve the problem of baselining...

What I am referring to is that before you upgrade, you can save a baseline config/Software plugin versions. if the upgrade (ANY upgrade) fails, just rollback to the previous in time.

I do understand and I am clear about that once the Kernel has been moved to from 21 to 22 then there's no going back... so yeah reinstall. However, when patching between 21.1.9 fails it should be super simple to rollback to 21.1.7 or any other that the user decides to maintain in revision...

I understand the need to have a enterprise-ready fallback and recover built into the software, but in the open source scope that is just not reasonable.

21.7 brings native ZFS install and you can do your snapshots there. It's still manual, but so are all other methods that have been proven to work reliably.

That being said 21.1 sounds fancier than it is since we do not change OS versions or cross any ABI barrier that would break post-update if it would not upgrade cleanly for whatever reason.


Cheers,
Franco

Is it possible to convert to zfs or is a total reinstall required for this option?


Quote from: franco on July 28, 2021, 08:01:42 PM
Needs a reinstall.

Thanks for taking the time to reply :)

Makes sense. Maybe I will look into this in the future. Right now upgrading is very stable even when things go wrong so will continue as is for now :)

Quote from: franco on July 28, 2021, 07:56:15 PM
I understand the need to have a enterprise-ready fallback and recover built into the software, but in the open source scope that is just not reasonable.

21.7 brings native ZFS install and you can do your snapshots there. It's still manual, but so are all other methods that have been proven to work reliably.

That being said 21.1 sounds fancier than it is since we do not change OS versions or cross any ABI barrier that would break post-update if it would not upgrade cleanly for whatever reason.


Cheers,
Franco

So would that mean the business versions may have this feature enabled?

Not at this point, but having ZFS as an option in the upcoming business version 21.10 does pave the way for such a feature in the future.


Cheers,
Franco