package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
happened during do-release-upgrade
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: lxd 3.0.3-0ubuntu1~
ProcVersionSign
Uname: Linux 4.15.0-117-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckR
Date: Sat Sep 12 14:01:45 2020
Ec2AMI: ami-0000be99
Ec2AMIManifest: FIXME
Ec2Availability
Ec2InstanceType: vps-ovhssd2018-3
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
ErrorMessage: new lxd package pre-installation script subprocess returned error exit status 1
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageV
dpkg 1.19.7ubuntu3
apt 2.0.2ubuntu0.1
SourcePackage: lxd
Title: package lxd 3.0.3-0ubuntu1~
UpgradeStatus: Upgraded to focal on 2020-09-12 (0 days ago)
tags: | removed: need-duplicate-check |
Re-assigned to snapd as the error was:
``` /api.snapcraft. io/v2/snaps/ refresh: dial tcp: lookup
api.snapcraft. io: device or resource busy
error: cannot install "lxd": Post https:/
```
And this was after passing the store connectivity check (snap info).
`device or resource busy` is a rather weird one for a connection failure, so I'm not sure what that's about and maybe snapd ought to attempt a retry on such failure?
In any case, I would expect re-trying the upgrade to succeed, assuming this was indeed a transient error coming from store communication.