'c' above can also be: 'sudo snap install'
There, the install wont complain or fail, but running 'hello' will.
$ sudo snap install hello
2018-10-11T17:54:21Z INFO Waiting for restart...
hello 2.10 from 'canonical' installed
$ echo $?
0
$ hello
cannot create lock directory /run/snapd/lock:
In another re-create scenario, you can see this fail on bionic.
a.) launch bionic image somewhere
b.) sudo sh -xc 'echo overlayroot=tmpfs > /etc/overlayroot.local.conf && reboot'
c.) $ sudo snap install lxd
2018-10-11T17:44:22Z INFO Waiting for restart...
error: cannot perform the following tasks:
After above recreate, you can login on console as 'root' with
'passw0rd'.
You'll then see the system is still 'starting' (per systemctl status)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797218
Heres an even easier re-create
$
url=http://cloud-images.ubuntu.com/cosmic/current/cosmic-server-cloudimg-amd64.img
$ img=${url##*/}
$ wget "${url}" -O "$img"
$ sudo mount-image-callback "$img" -- \
mchroot sh -xc 'echo overlayroot=tmpfs > $1 && echo root:$2 | chpasswd' \
setup-image
(installation via maas)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797218
Title:
boot hangs in curtin vmtest
To manage notifications about this bug go to:
I am attempting to verify if installation of 18.10 is similarly broken.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797218
Title:
boot hangs in curtin vmtest
To manage notifications about this
I noticed that the seeding of snaps in the cloud image also caused regression
of the open-iscsi test [1] as seen from [2].
If anyone wants to debug this the open-iscsi test case provides doc on
how to run it at [3] and I have a gist on it at [4].
Alternatively you can use uvt-kvm or multipass or
Looking at this bug:
https://bugs.launchpad.net/snappy/+bug/1665808
As we're in the same maas ephemeral environment; though we get a
slightly different error. However the workaround included:
sudo apt-get install -yu apparmor-utils
sudo aa-complain /usr/lib/snapd/snap-confine
does allow lxd
The error I see is:
Run install hook of "lxd" snap if present
2018-10-10T20:06:30Z ERROR run hook "install": cannot create lock
directory /run/snapd/lock: Permission denied
$ ls -al /run | grep snapd
srw-rw-rw- 1 root root0 Oct 10 20:06 snapd-snap.socket
srw-rw-rw- 1 root root0 Oct 10
$ snap changes
ID Status Spawn Ready Summary
1Error today at 19:46 UTC today at 19:47 UTC Initialize system state
2Donetoday at 19:46 UTC today at 19:46 UTC Initialize device
3Error today at 19:52 UTC today at 19:52 UTC Initialize system
$ for service in $(cd /lib/systemd/system && ls snap*); do echo $service
=; systemctl status --no-pager --full $service; done 2>&1 | pastebinit
http://paste.ubuntu.com/p/57W9QnXwfQ/
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
** Changed in: snapd (Ubuntu)
$ systemctl status snapd --no-pager --full
● snapd.service - Snappy daemon
Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset:
enabled)
Active: active (running) since Wed 2018-10-10 19:47:19 UTC; 44s ago
Main PID: 1960 (snapd)
Tasks: 11 (limit: 1105)
Memory:
Jenkins jobs that run this are archived at
https://jenkins.ubuntu.com/server/job/curtin-vmtest-devel-amd64/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797218
Title:
boot hangs in curtin vmtest
13 matches
Mail list logo
