Public bug reported:
Since some time over the holidays I've had problems
refreshing/installing the Wekan snap [1] on my home server and also my
desktop. The installation stalls at the configuration phase, which on
the surface looks a bit like bug #1674193 [2], but here core gets
installed just fine, and the hang occurs just alike if I first install
just core, then the `wekan` snap separately.
14.52 jani@saegusa:~$ sudo snap install wekan
[sudo] salasana henkilölle jani:
error: cannot perform the following tasks:
- Run configure hook of "wekan" snap if present (run hook "configure":
<exceeded maximum runtime of 5m0s>)
Installing other snaps works (the couple that I tried just to be able to say
this did anyway).
I've reported this on the Wekan snap Github page [3], but there's been
no confirmation from anyone else affected so far. Also, I'm unable to
reproduce this myself in a VM and on at least one other (physical)
desktop I have access to.
So naturally I've looked for differences between these systems, but so
far the only correlating one I'm pretty sure of is an Apparmor denial:
apparmor="DENIED" operation="open" profile="snap.wekan.mongodb"
name="/sys/block/" pid=9478 comm="mongod" requested_mask="r"
denied_mask="r" fsuid=0 ouid=0
The two systems where Apparmor denies mongodb's access to /sys/block get
stuck at the configure hook, whereas systems that don't deny access
finish the configuration (and installation) successfully.
I have not tweaked any Apparmor configuration on any of these systems
prior to this issue cropping up (not that I can remember anyway). I've
also not touched anything snap-related, as Wekan was one of the first
snaps I've ever tried and is (or would be) the only one (besides core)
currently installed on these systems.
All systems are running Ubuntu 16.04, with my (affected) desktop having
both HWE and -proposed enabled, my (affected) server running a
4.4-series kernel (no HWE or -proposed) and the other (unaffected)
desktop having HWE but no -proposed. The (unaffected) VM starts with
kernel 4.4 and remains unaffected if I upgrade it with HWE.
I'm submitting this from the (HWE+proposed-enabled) desktop, so any logs
attached here are from one of the two affected systems. I'll of course
provide other logs too if requested.
* [1] https://snapcraft.io/wekan/
* [2] https://bugs.launchpad.net/snappy/+bug/1674193
* [3] https://github.com/wekan/wekan-snap/issues/25
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: snapd 2.29.4.2
ProcVersionSignature: Ubuntu 4.13.0-30.33~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-30-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Jan 22 15:44:20 2018
InstallationDate: Installed on 2016-10-13 (466 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
SourcePackage: snapd
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.X11.Xsession.d.65snappy: 2018-01-19T18:18:12.001969
mtime.conffile..etc.apparmor.d.usr.lib.snapd.snap-confine.real:
2018-01-22T15:46:34.793893
** Affects: snapd (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744718
Title:
Install/refresh stuck at configure hook (Wekan)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1744718/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
