package lxd (not installed) failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1

Bug #1903367 reported by Andrei Coada
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snapd (Ubuntu)
New
Undecided
Unassigned

Bug Description

A simple 'do-release-upgrade' from 18.04 to 20.04

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: lxd (not installed)
ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18
Uname: Linux 4.15.0-122-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Nov 7 00:36:31 2020
ErrorMessage: new lxd package pre-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2019-01-22 (654 days ago)
InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt 2.0.2ubuntu0.1
SourcePackage: lxd
Title: package lxd (not installed) failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to focal on 2020-11-06 (0 days ago)

Revision history for this message
Andrei Coada (raziel.kernel) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Stéphane Graber (stgraber) wrote :

error: cannot perform the following tasks:
- Setup snap "snapd" (9721) security profiles (cannot run udev triggers for input subsystem: exit status 1
udev output:
Failed to write 'change' to '/sys/devices/virtual/input/input5/uevent': Cannot allocate memory
)

That's a new one, it may be related to a kernel issue in this case or even hardware.

In any case, as it's not even hitting on the LXD snap, re-assigning to snapd.

affects: lxd (Ubuntu) → snapd (Ubuntu)
Revision history for this message
Andrei Coada (raziel.kernel) wrote :

Quote:
"it may be related to a kernel issue in this case or even hardware."

I think this is a strong possibility.
The system is hosted on an old Xen hypervisor (although, I've never had this problem before, updating other VMs from 18.04 to 20.04).
Maybe it was a transient quirk. I still was able to finish the update successfully, nevertheless.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.