Traceback (most recent call last):
File "/usr/local/sbin/apt-upgrade", line 286, in <module>
main()
File "/usr/local/sbin/apt-upgrade", line 272, in main
cache.open(None)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 154, in open
self._records = apt_pkg.PackageRecords(self._cache)
SystemError: E:Could not open file /var/lib/apt/lists/nova.clouds.archive.ubuntu.com_ubuntu_dists_trusty_universe_i18n_Translation-en - open (2: No such file or directory), E:Could not open file /var/lib/apt/lists/nova.clouds.archive.ubuntu.com_ubuntu_dists_trusty_restricted_i18n_Translation-en - open (2: No such file or directory), E:Could not open file /var/lib/apt/lists/nova.clouds.archive.ubuntu.com_ubuntu_dists_trusty_multiverse_i18n_Translation-en - open (2: No such file or directory), E:Could not open file /var/lib/apt/lists/nova.clouds.archive.ubuntu.com_ubuntu_dists_trusty_main_i18n_Translation-en - open (2: No such file or directory)Description
Description
Event Timeline
Comment Actions
This is a known error. We suspect is produced because the apt-upgrade run has a race condition with puppet agent. Both procs update the apt cache, and if both are updating the apt cache at the same time, one of the process may see an invalid cache.
AFAIK, the python-apt library in use by apt-upgrade doesn't support any waiting or locking in case other proc is managing the apt cache, so we would have to write our own concurrency prevention mechanism if we conclude that the issue is indeed a race condition.
I would triage this task as low priority, since it really doesn't hurt us, just run again apt-upgrade or run it without updating the cache (the -u option) since it's usually fresh thanks to puppet.