Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1871487
Title:
anon_inode:[eventfd] leaked on vgs invocation inside lxd container
Status in lvm2 package in Ubuntu:
The main leak was in dqlite and has now been included in master, the
next rebuild of the snap (likely later today) will include it.
** Changed in: lxd (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
https://github.com/lxc/lxd/pull/7167
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1871487
Title:
anon_inode:[eventfd] leaked on vgs invocation inside lxd container
Status
https://github.com/canonical/raft/pull/123
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1871487
Title:
anon_inode:[eventfd] leaked on vgs invocation inside lxd container
Ok, can you post the output of "ls -lh /proc/PID/fd/" where PID is the
PID of the "lxd --logfile ..." process and the PID of the "daemon.start"
script (lxd's parent process)?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Will post each as separate comments as the others are long:
# ls -lah /proc/self/fd
total 0
dr-x-- 2 root root 0 Apr 9 21:23 .
dr-xr-xr-x 9 root root 0 Apr 9 21:23 ..
lrwx-- 1 root root 64 Apr 9 21:23 0 -> /dev/pts/4
lrwx-- 1 root root 64 Apr 9 21:23 1 -> /dev/pts/4
lrwx-- 1
lxc info:
config:
core.https_address: '[::]:8443'
core.trust_password: true
api_extensions:
- storage_zfs_remove_snapshots
- container_host_shutdown_timeout
- container_stop_priority
- container_syscall_filtering
- auth_pki
- container_last_used_at
- etag
- patch
- usb_devices
-
Not sure why it would make a difference, but just in case, I can also
reproduce this against a local container (rather than a remote one).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
And I just did a `lxd init --auto` on a fresh EC2 instance and I can
also reproduce it there.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1871487
Title:
$ lxc info reproducer
Name: reproducer
Location: none
Remote: https://34.76.172.211:8443
Architecture: x86_64
Created: 2020/04/09 21:22 UTC
Status: Running
Type: container
Profiles: default
Pid: 16441
Ips:
eth0: inet10.160.29.12veth12a00fff
eth0: inet6
Can you show `lxc info` please as well as `ls -lh /proc/self/fd` inside
that "reproducer" container?
I just tested it here and I'm seeing:
```
root@bionic:~# ls -l /proc/self/fd
total 0
lrwx-- 1 root root 64 Apr 9 20:57 0 -> /dev/pts/1
lrwx-- 1 root root 64 Apr 9 20:57 1 -> /dev/pts/1
Thanks Alasdair, I've added a lxd task.
** Also affects: lxd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1871487
The message is warning you that whatever process launched 'vgs' leaked a
file descriptor i.e. it has granted 'vgs' access to a file that should
not be there.
So you'll want to move this bug to whichever component that is e.g.
something related to 'lxc'
--
You received this bug notification
13 matches
Mail list logo
