kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #165512
[Bug 1551854] Re: LXD bootstrap issues on xenial
Haven't seen it in a few days. I'll reboot and see if I can reproduce
it. It usually happens after rebooting the host, when launching new
containers or existing ones would autostart.
Info you requested. I think the /usr/share/lxc/... might have been a red
herring. I'm exclusively using LXD on this xenial host, not messing with
the old lxc commands.
$ dpkg -l lxc liblxc1 lxd lxd-client lxcfs
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===============================-====================-====================-====================================================================
ii liblxc1 2.0.0~rc5-0ubuntu1 amd64 Linux Containers userspace tools (library)
ii lxc 2.0.0~rc5-0ubuntu1 all Transitional package for lxc1
ii lxcfs 2.0.0~rc2-0ubuntu2 amd64 FUSE based filesystem for LXC
ii lxd 2.0.0~rc1-0ubuntu3 amd64 Container hypervisor based on LXC - daemon
ii lxd-client 2.0.0~rc1-0ubuntu3 amd64 Container hypervisor based on LXC - client
$ lxc info
apicompat: 0
auth: trusted
environment:
addresses:
- 192.168.88.234:8443
- 192.168.122.1:8443
- 10.0.3.1:8443
architectures:
- x86_64
- i686
certificate: |
-----BEGIN CERTIFICATE-----
MIIFqjCCA5KgAwIBAgIQXpne6Qjwhg8de+RmyV1+mTANBgkqhkiG9w0BAQsFADA6
MRwwGgYDVQQKExNsaW51eGNvbnRhaW5lcnMub3JnMRowGAYDVQQDDBFyb290QG1h
d2hyaW4tc2tlbDAeFw0xNjAyMjgwMzEyMzdaFw0yNjAyMjUwMzEyMzdaMDoxHDAa
BgNVBAoTE2xpbnV4Y29udGFpbmVycy5vcmcxGjAYBgNVBAMMEXJvb3RAbWF3aHJp
bi1za2VsMIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEAzv/3uX3JWduq
wmtbyTABmfJkup6Z5Lh4lKPXgL/H2gQ/mlccORKm1eDZhAGmv9UuQGeMRHEneJqD
V9c3f7/9cJBwvz2loKlppWj0ohAzTP91L8paeUSfP4X9EAr702Qjyb2ig+xWv5tM
cJxbdl0zGpjYO1P+xmUdthSidsFrzWQPXptOlcZvak7n0QL5GlkVXdqX+she2Pbs
ONtyTaBSpF3zEYv6cM9ZeJYL4Hl7LEQ1/p8ojpOyaxO8B1Cn/gIbuDqgzRwmei90
Aca06YDF4SHVcl8qFajrwkPF3jWW5pgS8sAJlYoq2+ROhl0CnpdBl4AiJrvfFsIs
RL8dKSuFA6AcLhYooWgMy6UWR8mLbmYHp04ThuBDoRaTt0uGLDlTAfMg7e8Gwpz+
aEwxSzzQhvJYr4e6TSP1C4zXNqS5mUHfm6RtfEccVFmq6vyqZGELAyREce76J88V
FMf/V+KYlQYUxo0JH2k+BYMO4Iigar0+8p8o8drqh6Lks5zTP6idsKa0LSWA4rwm
3+5hjnVJtFa9CVCItJW3r0+nczwtAbjvRojkr7Yb2Kifufhilb+I695qSk+Toug3
HKOODTqc9sbH+urmfr7jBBexACtWVX/tMptWFnBmcqoN4ptSZutY7CPf+KR//9p0
8fFRQP+ItmElJHRFO+madGOBMVrC7j8CAwEAAaOBqzCBqDAOBgNVHQ8BAf8EBAMC
BaAwEwYDVR0lBAwwCgYIKwYBBQUHAwEwDAYDVR0TAQH/BAIwADBzBgNVHREEbDBq
ggxtYXdocmluLXNrZWyCETE5Mi4xNjguODguMjM0LzI0ghxmZTgwOjozZWE5OmY0
ZmY6ZmU1Njo0N2RjLzY0ggsxMC4wLjMuMS8yNIIcZmU4MDo6NThkNTpjMmZmOmZl
ZTQ6NzJiYy82NDANBgkqhkiG9w0BAQsFAAOCAgEAB6aFItuxlZm5+2/IB2eCVAM0
eQbO6dfvfF2khfiEbWWaKPtkZSYKlDIcoOph35obnNMQjT+y4zlnF/fepvjq8P1R
yGd+Q+GMcXWVRht3uIMW2ZqwNqOujunyn9+Hl1SYi1dV1g/CH9lJt8I7FKIvyieh
siZRe5Zp7TdPREkIJveuz8qB3X87WVh9bqvMpoX91Mgrjzd3qATef/tN0HP+b26Y
XjtRz9rhOkUfJx9b5HsyBLuGOQS979twl9LPKc1WsIrJaavY1JBT7SIwX3W7u7CU
UWueEQoVvA9pkgeL8NXYYoHOkkrfW3oqExkuA1pqucMt8iRjn88njV57Vk576tjZ
+bNqLL6R4xoUvnr9VIwq7tMLvodK/E5WvsmP5GrdMru2sa/xd+fS0137oOYqP4Qb
T296jMcehHg5Gg1ZR1DbTqzWFPKb+CtXU+bqI68Hplq5Lemufsman2C2dthmKwcm
OumpykWiH9vNKauY52VR8iffppBsH7jup1+yVtIOiT4Whp5LGBtZdYri7GE77qv+
qtBL7HdeBJxsBadRIfjdeLZlZPlMX7hV+v8Bzxz9fGuPKSnxDdpoPw1XF+zP1YAn
VeDCRo7oCFV40nVFyb5wCreDoegtSFuQt7/Guv9u/gQSfmGoY1QyjlaHh2pJAAgS
CPRGObnrdrQMMEqLDaI=
-----END CERTIFICATE-----
driver: lxc
driverversion: 2.0.0.rc5
kernel: Linux
kernelarchitecture: x86_64
kernelversion: 4.4.0-10-generic
server: lxd
serverpid: 2382
serverversion: 2.0.0.rc1
storage: zfs
storageversion: "5"
config:
core.https_address: '[::]'
storage.zfs_pool_name: lxdpool
public: false
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1551854
Title:
LXD bootstrap issues on xenial
Status in linux package in Ubuntu:
Incomplete
Bug description:
I'm using lxd with zfs block storage on xenial, and having issues with
trusty containers. I've witnessed this problem when trying to
bootstrap as well as after rebooting the host and a container failed
to start.
In the latter case, the container that failed to start was the juju
controller:
c@mawhrin-skel:~/omnibus-layers$ lxc list [3/3]
+-----------------------------------------------------+---------+--------------------------------+------+------------+-----------+
| NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS |
+-----------------------------------------------------+---------+--------------------------------+------+------------+-----------+
| juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0 | STOPPED | | | PERSISTENT | 0 |
+-----------------------------------------------------+---------+--------------------------------+------+------------+-----------+
| juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-1 | RUNNING | 10.0.3.28 (eth0) | | PERSISTENT | 0 |
+-----------------------------------------------------+---------+--------------------------------+------+------------+-----------+
| juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-2 | RUNNING | 10.0.3.85 (eth0) | | PERSISTENT | 0 |
+-----------------------------------------------------+---------+--------------------------------+------+------------+-----------+
| juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-3 | RUNNING | 10.0.3.176 (eth0) | | PERSISTENT | 0 |
+-----------------------------------------------------+---------+--------------------------------+------+------------+-----------+
| juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-4 | RUNNING | 10.0.3.66 (eth0) | | PERSISTENT | 0 |
+-----------------------------------------------------+---------+--------------------------------+------+------------+-----------+
| juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-5 | RUNNING | 10.0.3.31 (eth0) | | PERSISTENT | 0 |
+-----------------------------------------------------+---------+--------------------------------+------+------------+-----------+
| juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-6 | RUNNING | 10.0.3.196 (eth0) | | PERSISTENT | 0 |
+-----------------------------------------------------+---------+--------------------------------+------+------------+-----------+
| juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-7 | RUNNING | 10.0.3.186 (eth0) | | PERSISTENT | 0 |
| | | 10.0.4.1 (lxcbr0) | | | |
+-----------------------------------------------------+---------+--------------------------------+------+------------+-----------+
I manually started it, but found that no upstart services were
started. Remembering this thread,
https://lists.ubuntu.com/archives/juju/2016-February/006698.html, I
checked /var/log/mountall.log in the machine-0 container, and sure
enough:
root@juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0:~# cat /var/log/upstart/mountall.log
mount: permission denied
mountall: mount /sys/kernel/debug [187] terminated with status 32
mountall: Filesystem could not be mounted: /sys/kernel/debug
The problem persists if I stop and start the container. If I remount
/sys/kernel/debug on the host, then stop and start the container,
upstart succeeds and the juju controller starts up.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-8-generic 4.4.0-8.23
ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
Uname: Linux 4.4.0-8-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: c 24562 F.... pulseaudio
CurrentDesktop: MATE
Date: Tue Mar 1 10:52:45 2016
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=007cedda-f922-4e4c-89b1-57b31f18292e
InstallationDate: Installed on 2016-02-28 (2 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
MachineType: LENOVO 2306CTO
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-8-generic.efi.signed root=/dev/mapper/ubuntu--mate--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.4.0-8-generic N/A
linux-backports-modules-4.4.0-8-generic N/A
linux-firmware 1.156
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/22/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ETA1WW (2.61 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2306CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrG2ETA1WW(2.61):bd04/22/2014:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2306CTO
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1551854/+subscriptions
References
