Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
Turris OS packages
Turris OS packages
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 87
    • Issues 87
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 17
    • Merge Requests 17
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Turris
  • Turris OS packagesTurris OS packages
  • Issues
  • #344

Closed
Open
Opened Mar 26, 2019 by Karel Koci@kkoci🤘Owner34 of 41 tasks completed34/41 tasks

Migration from 3.x to 5.x

There were some configuration changes in OpenWRT in meantime and we should implement script that migrates those primary settings

  • Switch configuration is now done using DSA and switch sections are obsolete. We have to migrate them.
  • Create new bridge interface for VLANs without CPU port assigned. (won't be implemented unless wide deployment with such config is discovered)
  • Updater configuration and userlists to pkglists
  • Wifi paths migration (option path 'soc/soc:pcie-controller/pci0000:00/0000:00:01.0/0000:01:00.0' vs option macaddr '04:f0:21:1c:b7:52')
  • Detect and select sfp

Known problems:

  • update takes a long time because ubus seems to be timing out. I is enough to kill ubusd when new version is installed.
  • base-files with /etc/services_wanted is updated later in update and because of that some services (syslog-ng, dnsmasq, ...) are not activated. turris-build@154d9217)
  • some services like lighttpd and mysql are ordered before ubus update do they postinst scripts are hanging (on procd timeout) (solution: turris/updater/updater#137)
  • services are still not enabled even with fix from previous line (solution: turris/updater/updater#273 (closed))
  • after migration Foris reports LAN and guest as to not contain any interface. This is because it expects ifname as list not option.
  • region country is not set in Foris. This is because of missing system[0]._country option but do we care? (this is because it wasn't set in 3.x. If set then it is correctly carried over)
  • nextcloud does not work after update. Website is empty. (#431 (closed))
  • single interface in network should be option not list otherwise wan dhcp proto does not work (a9ec3c8b)
  • knot resolver is unreachable for some reason (problem was in loopback not having interface)
  • /etc/config/fstab field uuid now really uses UUID and not subuuid (SUBUUID drives are not mounted. We should replace SUBUUIDs with UUIDs) (Unconfirmed)
  • User installed packages that are no longer available in 4.0+ should be removed/disabled somehow or we should not initialize update. (turris-build!59 (closed), turris-build!107 (merged))
  • updater is unable to found localrepo repositories (!168 (merged))
  • localrepo contains invalid packages (we should just flush localrepo and inform user about it)
  • localrepo fix to move it away does not work sometimes (!374 (merged))
  • LXC is not reportedly migrated (but script itself works as users suggesting them self to run it manually) (!369 (merged))
  • Turris 1.x currently can't be migrated because of dependency loop on updater-ng package (turris-build!183 (merged), turris-build!187 (merged))
  • Scary message about removal of turris-btrfs is send to users of Turris 1.x because of rename of that package
  • Migration breaks (with broken libraries) because of !417 (merged) if package depending on knot-libs is installed (resolved by turris-build!196 (merged))
  • Some swconfig configuration might stay in place (we might be ignoring it) and it can cause problems with system without swconfig (commands failing) (resolved by !383 (merged))
  • Notify users about finished migration (probably on tos3to4 package removal) (!380 (merged))
  • Wireguard DEVICE_CLAIM_FAILED error after migration (#696 (closed) #697 (closed))
  • Alternatives are not updated after migration as well as on Turris 1.x new version of kernel is not as well (turris/updater/updater#309 (closed) #678 (closed))

Test:

  • basic network configuration (switch, bridges, ..)
  • guest wifi and network configuration
  • firewall rules
  • DNS configuration
  • openvpn
  • pakon
  • storage plugin
  • lxc
  • haas (honeypot as a service)
  • netmetr
  • nextcloud
  • localrepo
  • dev detect (migration from pakon-dev-detect to dev-detect)
  • mwan

Things to notify users about:

  • Updater approvals are disabled for this migration to mitigate possibility that because of link dependencies the approve would be impossible to give. Notification about it is send to notification system once user installs tos3to4 on Turris OS 3.x.
  • Updater is reported as disabled during update.
Edited Nov 20, 2020 by Karel Koci
Assignee
Assign to
Turris OS 3.x migration
Milestone
Turris OS 3.x migration (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: turris/turris-os-packages#344