I can confirm it works.
The rocky-proposed package python-oslo.cache-1.30.1-0ubuntu1.1 fixes bug
#1822541 too.
I manually upgraded the n-c-c units on a Rocky cloud (applying the
proper bindings for n-c-c & memcached according with the comment #14 of
bug #1823740) to get the new python-oslo packag
Running the containers 'init' operation in the concurrent way and
looking with a 'top', you can see the related 'unsquashfs' operations
running:
for X in `seq 1 4`; do lxc init ubuntu: test$X & done
top
Waiting until the unsquashfs terminates and then starting the
containers, all is good and the
Yes, I unmounted it.
getfacl: Removing leading '/' from absolute path names
# file: var/lib/lxd/storage-pools/default/containers/test1
# owner: 10
# group: 10
user::rwx
user:10:r-x
group::r-x
mask::r-x
other::r-x
--
You received this bug notification because you are a member of Ubunt
VM upgraded to:
Linux ubuntu 4.4.0-66-generic #87
Same behaviour.
Here attached the output of the 'ls' commands.
** Attachment added: "lxd.listing"
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1675760/+attachment/4844752/+files/lxd.listing
--
You received this bug notification becau
Here attached there is the log of a single container (test1), as
requested by Christian.
lxc info --show-log test1
** Attachment added: "'test1' container log"
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1675760/+attachment/4844639/+files/test1.log
--
You received this bug notificati
cat /proc/self/mounts
http://pastebin.ubuntu.com/24241515/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675760
Title:
rootfs issues - 2.8 LXD release
To manage notifications about this bug go t
'lxc info' output:
http://pastebin.ubuntu.com/24241376/
'lxc config show' output:
http://pastebin.ubuntu.com/24241379/
I ran:
for X in `seq 1 4`; do lxc init ubuntu: test$X & done
and then, after a while:
for X in `seq 1 4`; do lxc start test$X & done
This is what I got in the /var/log/lxd/
A freshly created one (KVM VM). LXD 2.12
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675760
Title:
rootfs issues - 2.8 LXD release
To manage notifications about this bug go to:
https://bugs.lau
We ran new tests: some issue shows up even using LXD 2.12
If I run:
for X in `seq 1 4`; do lxc init ubuntu: test$X & done
LXD creates the containers but it can't start them.
This is the output of 'lxc info --show-log test1':
https://pastebin.canonical.com/183666/
If I run:
for X in `seq 1 4
Public bug reported:
System:
Distributor ID: Ubuntu
Description:Ubuntu 16.04.2 LTS
Release:16.04
Codename: xenial
Kernel release: 4.8.0-36
LXD release 2.8
I got a rootfs error starting few LXD containers:
https://pastebin.canonical.com/183648/
This is the 'lxc list' output:
the late_command curtin line should be also set in
/etc/maas/preseeds/curtin_userdata
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590689
Title:
MAAS 1.9.3 + Juju 1.25.5 - on the Juju controller n
Public bug reported:
Ubuntu 14.04.4 and SRIOV settings.
As already documented in https://bugs.launchpad.net/mos/+bug/1501738
there is a bug in the default libnl library release installed on Ubuntu
14.04.4
The library release is the 3.2.21-1 and the bug is impacting on the
maximum VFs number that
12 matches
Mail list logo
