I want to congratulate to whole Turris team on the automated Omnia migration to OS 5.x.
I postponed this indefinitely, just being scared of the manual migration to miss some of my custom settings and losing them by the upgrade…
Today, I found in my email inbox a message:
Migration from Turris OS 3.x was completed.
Great work, I haven’t found any lost configuration, custom subnets, routing, samba shares were preserved. Despite a potential issues found later, I’m impressed by the great work done. Thanks a lot to the whole Turris team!
I totally agree.
Admitted, mine is a standard installation, the only relevant change from the original system was setting a VLAN tag as needed in Germany because Telekom sends every packet in VLAN 7.
Still, the automated migration would have gone totally unnoticed if my Turris Omnia wouldn’t have sent mails. (And if I wouldn’t periodically check the installed software versions.)
I really feel protected by the Omnia and its continuous software maintenance, which means I need not spend effort in the maintenance myself. Wonderful!
A Merry Christmas to all of you, a sincere “Thank You!” to the team,
and may the virus keep far away from you all!
Jörg Brühe
Mine went horribly wrong… having originally WAN configured over LAN2 (due to another ISP link connected to WAN that is no longer operational) endup stuck in middle of upgrade, as no internet was connected after reconfiguration. Having no direct access to Turris I had to lead onsite how to fix that thing In the end I also found that OpenVPN and BIRD packages (unknown architecture error or something, I think this is just because turris lost internet connection after reconfiguration script kicked in) were not installed, but it was just a cherry on a cake to fix once I got remote desktop shared to access internal network.
Would be lovely if those update scripts just stop when encounter non-standard configuration and inform user to upgrade manually.
I agree with more careful approach to major updates. The main problem is that the Turris team supports only configuration changes done through Web UI (Foris or LuCI), which, although understandable from the maintenance costs and sourcing perspectives, ignore many community power users who configure the router on command line.
In my case, I lost LXC services and was able to fix that quickly (details at Upgrade from 3.x to 5.2.3 and LXC problems), but the problem is that potentially problematic upgrade was rolled out automatically without me being able to account for that.
I would strongly prefer to be able to opt-out of automatic major version upgrades so I can plan for them and upgrade only when I’m ready to spend time on potential fixes.
However, complaints aside, thanks the Turris team for all the work!
Since June 2020, we announced the possibility to migrate from Turris OS 3.x. We informed our users on social media networks like Twitter, Facebook, etc.
We also sent in September 2021 at least two notifications that the migration is available and that it needs to be triggered manually.
And in December, we released migration automatically by waves to be sure that it works and receive feedback to be able to fix issues, which could appear.
It seems you understand why we need to migrate users from the old stable version to a new one. We need to cover configurations where users plugged the router into the Internet and almost forgot about their device. If you lost only LXC services, I would say that overall it was smooth for you. Always, it can be better or worse.
Migration went OK on Turris 1.0.
SDCard was corrupted, so I did card replacement + factory reset.
The biggest issue was self update from 3.5.8 to 3.11.23 after factory reset (I guess DNSSec with old certs, leads to dns resolve issue during first time wizard).
Btrfs was migration is OK.
Automatic update from 3.11.23 done correctly.
Not-so-great, I am at the moment 3000km from our offices, one of routers upgraded automatically and we lost bird4 package - and all routes to private networks because of that. Sub-optimal, i would say, as at the moment, because of being so far away, i really do need remote accesses to work - I could take a car and ride to one of our offices in last months, but right now it’s totally impossible.
Any hints how to restore bird4?
# pkg info bird*
Package bird4 version 1.6.8-1 has no valid architecture, ignoring.
What’s more interesting, some routers (which had “automatic approval” enabled for updates) didn’t get 5.x (which is great, because they didn’t break because of the upgrade). However, foris->updater there shows only some lib pending, since 02/2021 (libopenssl, libcurl, libuci-lua, openssl-util, libuci, updater-ng). Would approving those updates cause a major upgrade to 5.x? If so, that could be communicated a little bit better If not, where is the “switch” that blocks/allows 5.x upgrade?
In the end I also found that OpenVPN and BIRD packages (unknown architecture error or something, I think this is just because turris lost internet connection after reconfiguration script kicked in) were not installed, but it was just a cherry on a cake to fix once I got remote desktop shared to access internal network.
