/usr/bin/unattended-upgrade:apt.cache.CacheClosedException:/usr/bin/unattended-upgrade@2512:main:run:do_auto_remove:cache_commit:commit:_fetch_archives

[errors.ubuntu.com bug bridge]

Traceback (most recent call last):
  File "/usr/bin/unattended-upgrade", line 2512, in <module>
    sys.exit(main(options))
  File "/usr/bin/unattended-upgrade", line 1986, in main
    res = run(options, rootdir, mem_log, logfile_dpkg,
  File "/usr/bin/unattended-upgrade", line 2307, in run
    kernel_pkgs_kept_installed) = do_auto_remove(
  File "/usr/bin/unattended-upgrade", line 1876, in do_auto_remove
    res, error = cache_commit(cache, logfile_dpkg, verbose)
  File "/usr/bin/unattended-upgrade", line 861, in cache_commit
    res = cache.commit(install_progress=iprogress)
  File "/usr/lib/python3/dist-packages/apt/cache.py", line 678, in commit
    res = self._fetch_archives(fetcher, pm,
  File "/usr/lib/python3/dist-packages/apt/cache.py", line 466, in _fetch_archives
    raise CacheClosedException(
apt.cache.CacheClosedException: Cache object used after close() called

---

The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 2.1, the problem page at https://errors.ubuntu.com/problem/b923ed6f4c01a301c3d3910bdb0eed754b7214f7 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/.

[Balint Reczey (rbalint)]

Unattended-upgrades does not close the cache, so the closing may have been done by python-apt for some reason. It it is triggered by unattended-upgrades then u-u can try to avoid that.

Since it affects only autoremoval and the u-u can continue applying the the fixes in the next runs I'm marking this bug as low priority.