Skip to content

Upgrading plinth via upgrades module causes problems

Created by: SunilMohanAdapa

After fix the unattended upgrades module to run upgrades in background, two problems still remain:

  • If Plinth is upgraded during the upgrade process, the information we are using keeping track of the process is lost. Plinth interface shows upgrade as not running even though it is still running. It then allows spawning another upgrade process.
  • When upgrade process starts because of cron, in plinth, we are showing that the process as not started and allowing the start of another process.
  • When Plinth/Apache2 are restarted during the upgrade, the refresh cycle breaks.

Possible solutions:

  • For the first two problems, we can switch to identifying a running unattended-upgrades process in a different manner such as looking at process list in addition to what we are doing now. Result can perhaps be picked up from log files, if there is a reliable way of doing that. If unattended-upgrades use systemd unit file, all of this will be straight forward.
  • For third problem, we can warn the user that Plinth and other services may get disrupted during the upgrades and that she can refresh after a brief time.