marking as affecting kernel given the description.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1536280
marking as affecting kernel given the description.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536280
Title:
domain
Thanks for reporting this bug - I will work on reproducing later today.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1536331
Title:
Precise to Trusty live migration failing
To
Thanks for reporting this bug - I will work on reproducing later today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536331
Title:
Precise to Trusty live migration failing
To manage
I'm also curious why the launchpad janitor marked this bug confirmed.
If anyone else can reproduce this issue, please comment here.
Otherwise, I do not want it marked confirmed until someone truly
independently reproduces it.
** Changed in: libvirt (Ubuntu)
Status: Confirmed => Incomplete
I still cannot reproduce this at all, even when starting VMs from virt-
manager.
Are you still able to reproduce this? (I'm wondering whether perhaps
there was a temporary bad state of systemd and libvirt being out of sync
some magical way)
--
You received this bug notification because you are
Quoting RussianNeuroMancer (1529...@bugs.launchpad.net):
> > I still cannot reproduce this at all, even when starting VMs from
> > virt-manager.
> Well, for fresh install this is not reproducible for me too. And 15.10-16.04
> upgrade may not be actual trigger - both testing systems get upgraded
@tkedwards,
Could you please show your cgmanager version?
dpkg -l | grep cgmanager
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1534090
Title:
'call to get_tasks_recursive failed' errors from su
Thanks - Martin - tested that with the mainline kernel, and it did indeed
give me a pids cgroup:
ubuntu@pitti:~$ cat /proc/self/cgroup
11:hugetlb:/user.slice/user-1000.slice/session-2.scope
10:blkio:/user.slice/user-1000.slice/session-2.scope
9:devices:/user.slice/user-1000.slice/session-2.scope
Thanks - Martin - tested that with the mainline kernel, and it did indeed
give me a pids cgroup:
ubuntu@pitti:~$ cat /proc/self/cgroup
11:hugetlb:/user.slice/user-1000.slice/session-2.scope
10:blkio:/user.slice/user-1000.slice/session-2.scope
9:devices:/user.slice/user-1000.slice/session-2.scope
Confirmed it happens for me with the lxd-git-master ppa.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1534090
Title:
'call to get_tasks_recursive failed' errors from su
To manage notifications
I'll remove all those error messages printed to stderr in pam/cgmanager.c. If
cgmanager
were going to last I would take the time to pass the errors back up to log them
to syslog,
but it's just not worth it.
** Changed in: cgmanager (Ubuntu)
Importance: Undecided => Medium
--
You received
Yup that'll get the update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1534090
Title:
'call to get_tasks_recursive failed' errors from su
To manage notifications about this bug go to:
Trusty doesn't have libpam-cgm. Do you mean in ppas?
** Also affects: cgmanager (Ubuntu Wily)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1534090
Trusty doesn't have libpam-cgm. Do you mean in ppas?
** Also affects: cgmanager (Ubuntu Wily)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cgmanager in Ubuntu.
Public bug reported:
In bug 1358835 we applied a fix to supress a warning. The patch is different
from upstream (and appears wrong).
In particular,
+ if (numa_bitmask_isbitset(numa_nodes_ptr, node)) {
becomes
+ if (f) {
Switch to a straight cherrypick of the
Public bug reported:
In bug 1358835 we applied a fix to supress a warning. The patch is different
from upstream (and appears wrong).
In particular,
+ if (numa_bitmask_isbitset(numa_nodes_ptr, node)) {
becomes
+ if (f) {
Switch to a straight cherrypick of the
The patch in our package has the upstream patch except for one apparent
error - it checks for
if (f)
instead of
if (numa_bitmask_isbitset(numa_nodes_ptr, node)) {
I think it will be easiest to open a new bug to fix that. I'll note the
new bug# here.
--
You received this bug
The patch in our package has the upstream patch except for one apparent
error - it checks for
if (f)
instead of
if (numa_bitmask_isbitset(numa_nodes_ptr, node)) {
I think it will be easiest to open a new bug to fix that. I'll note the
new bug# here.
--
You received this bug
Opened bug 1535494
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to numactl in Ubuntu.
https://bugs.launchpad.net/bugs/1358835
Title:
numa_node_of_cpu() returns warning when cpu_index > 79
To manage notifications about this bug go
Opened bug 1535494
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1358835
Title:
numa_node_of_cpu() returns warning when cpu_index > 79
To manage notifications about this bug go to:
Hi,
Can you show the result of doing
sudo kvm-ok
groups
and
kvm -vnc :1
** Changed in: qemu (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Given the affected releases are all EOL, I will mark this bug invalid.
If anyone still sees this happen, please re-open.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1122245
Title:
booting from a
Hi,
Can you show the result of doing
sudo kvm-ok
groups
and
kvm -vnc :1
** Changed in: qemu (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
Thanks for reporting this bug.
janv. 17 12:37:51 hostname libvirtd[22974]: Unable to initialize audit layer:
Permission non accordée
janv. 17 12:37:51 hostname libvirtd[22974]: cannot connect to netlink socket
with protocol 0: Permission non accordée
Can you show what happens when you type
** Also affects: init-system-helpers (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533839
Title:
vms shutting down on libvirt upgrade
To
** Also affects: init-system-helpers (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to init-system-helpers in Ubuntu.
https://bugs.launchpad.net/bugs/1533839
Title:
vms shutting
The bug was fixed in vivid (and later). Which libvirt version are you
using?
It sounds like we need to SRU this to trusty.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
https://bugs.launchpad.net/bugs/1432644
The bug was fixed in vivid (and later). Which libvirt version are you
using?
It sounds like we need to SRU this to trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1432644
Title:
VM
(If the bug ends up being only the warning message, than it is fix
released and low priority. If there is a problem affect lxc startup,
then it is high priority)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
(If the bug ends up being only the warning message, than it is fix
released and low priority. If there is a problem affect lxc startup,
then it is high priority)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
(Firing up a vm to reproduce)
The error message has been fixed in 0.39-2ubuntu4 uploaded today to
xenial.
Can you show your /proc/self/cgroup output? Mine shows
ubuntu@beret:~$ cat /proc/self/cgroup
11:blkio:/user.slice
10:hugetlb:/
9:memory:/user.slice
8:cpu,cpuacct:/user.slice
7:perf_event:/
to dh_systemd_start
+
+ -- Serge Hallyn <serge.hal...@ubuntu.com> Sat, 16 Jan 2016 00:42:51 +
+
init-system-helpers (1.24ubuntu2) xenial; urgency=medium
* Add Breaks/Replaces on upstart to cover move of
diff -Nru
init-system-helpers-1.24ubuntu2/patches/fix-systemd-restart-on-upgrade.patch
init-
to dh_systemd_start
+
+ -- Serge Hallyn <serge.hal...@ubuntu.com> Sat, 16 Jan 2016 00:42:51 +
+
init-system-helpers (1.24ubuntu2) xenial; urgency=medium
* Add Breaks/Replaces on upstart to cover move of
diff -Nru
init-system-helpers-1.24ubuntu2/patches/fix-systemd-restart-on-upgrade.patch
init-
> Something I'm still not sure about is what would happen if you made a
> symlink, bind mount, etc. in upperdir with the same name as an unrelated
> file in lowerdir. This is worth checking out.
just tried a symlink and it didn't seem to affect the host directory
(/opt/cisco) which was symlinked
Thanks for submitting this bug.
Reproduce here.
** Changed in: libvirt (Ubuntu)
Importance: Undecided => High
** Changed in: libvirt (Ubuntu)
Importance: High => Critical
** Changed in: libvirt (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you
systemd should be updated to know about the pids cgroup
** Also affects: lxc (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Wily)
Importance: Undecided
Status: New
** Changed in: lxc (Ubuntu)
Status: Confirmed => Fix Released
**
(Note this should be properly handled in xenial, but needs fixing in
wily)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1533833
Title:
unprivileged lxc containers won't start
To
prior versions are doing it for me to.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533839
Title:
vms shutting down on libvirt upgrade
To manage notifications about this bug go to:
libvirt-bin.service has
Before=libvirt-guests.service
and libvirt-guests.service has
After=network.target libvirt-bin.service time-sync.target systemd-
machined.target
Does that sabotage the --no-restart-on-upgrade?
--
You received this bug notification because you are a member of Ubuntu
lv2 login: systemd-journald.service: Got notification message from PID 318
(WATCHDOG=1)
Accepted new private connection.
Got message type=method_call sender=n/a destination=org.freedesktop.systemd1
object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager
member=StopUnit
systemd should be updated to know about the pids cgroup
** Also affects: lxc (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Wily)
Importance: Undecided
Status: New
** Changed in: lxc (Ubuntu)
Status: Confirmed => Fix Released
**
(Note this should be properly handled in xenial, but needs fixing in
wily)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533833
Title:
unprivileged lxc containers won't start
To manage
You're using a newer kernel which provides the 'pids' cgroup. Systemd doesn't
know about that one and so doesn't create a cgroup for you that you own. Lxc
in turn (in wily) doesn't yet know how to handle that.
You can work around this several ways. The simplest is to do
sudo cgm create pids
You're using a newer kernel which provides the 'pids' cgroup. Systemd doesn't
know about that one and so doesn't create a cgroup for you that you own. Lxc
in turn (in wily) doesn't yet know how to handle that.
You can work around this several ways. The simplest is to do
sudo cgm create pids
Does it require the workdir to be empty?
I.e. is there a way (symlink, bind mount, something else) that a user
could use a dir they own which has a child which they don't own?
It looks like no, since
root@w1:/tmp# mount -t overlay -o lowerdir=lower,upperdir=upper,workdir=workdir
overlay /mnt
Thanks - it looks like libvirt is upset about something relating to
locales. What do
dpkg -l | grep language-pack
env | grep LANG
sudo env | grep LANG
show?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: libvirt (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1483071
Title:
Error creating new VM with OVMF
To manage
** Also affects: libvirt (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1483071
Title:
Error creating new VM with OVMF
Quoting Seth Forshee (seth.forshee...@canonical.com):
> I don't know why #2 is that much grosser than what's there now. It's
I didn't mean gross as in eeuw, I meant not fine-grained enough.
Because the capability will apply to inode permissions checks,
and we only want it to be used for the
in ovl_clear_empty(), the opaque bit is set on the dir in workingdir
in ovl_create_over_whiteout() (the case we're currently looking at) it is
also being set in the working dir.
in ovl_rename2(), it is set in two places, on the upper dentries for
both the old and new.
So it is never set on the
Anything more from
sudo journalctl -u libvirt-bin
How about
sudo strace -f /usr/sbin/libvirtd -v
for pete's sake.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1531833
Title:
** Description changed:
+ =
+ SRU Justification
+ Impact: cannot start VMs with UEFI
+ Test case:
+ Regression potential: virt-aa-helper is modified to add the nvram files to
the allowed list, there should be no regressions.
+ =
+
#2 is probably a bit too gross - we really only need the cap for the setting
of the OVL_XATTR_OPAQUE xattr in ovl_set_opaque. So we could simply override
creds again there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@mnaser,
We need a simple testcase in the Description for SRU. do you know the
minimal set of things needed to make this happen? Are you running an
unmodified ceph, or ceph from a particular ppa which re-enables lttng?
** Description changed:
+ =
+ SRU
@mnaser,
We need a simple testcase in the Description for SRU. do you know the
minimal set of things needed to make this happen? Are you running an
unmodified ceph, or ceph from a particular ppa which re-enables lttng?
** Description changed:
+ =
+ SRU
** Description changed:
+ ===
+ SRU Justification
+ Impact: snapshotting vms fails
+ Test case: install qemu-ga and use the snapshot-create-as command below
+ Regression potential: We broaden the types of sockets which virt-aa-helper
allows to include vhostuser.
** Description changed:
+ ==
+ SRU Justification
+ Impact: libvirt unable to grant access to hugepages
+ Fix: add an apparmor rule to allow libvirt to access hugepages at the path
which systemd uses
+ Test case: boot a vm with hugepages enabled.
+
Ok, I don't know why that won't give us the error output we're looking
for.
What happens when you just do
sudo /usr/sbin/libvirtd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1531833
Title:
hat may not be ok for the ovl_rename2 case.
What we want is for inode permissions to be checked, but only the
bit in xattr_permission() checking for trusted.* to accept ns_capable.
We could special-case that in xattr_permission(), but that's not
particularly nice.
--
You received this bug
Do you get more if you add '-v' ?
Also try setting
log_level = 1
in /etc/libvirt/libvirtd.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1531833
Title:
package libvirt-bin
Can you show 'ls /proc/$(pidof cgmanager)/fd' at a few times?
This is something we've run into with normal operation in go, but since
cgmanager is not threaded it should not have so many open fds.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Can you show 'ls /proc/$(pidof cgmanager)/fd' at a few times?
This is something we've run into with normal operation in go, but since
cgmanager is not threaded it should not have so many open fds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Ok, so this is working as expected. But I guess there is really zero
advantage to having a copy-clone on btrfs, so I think it's worth
changing.
status confirmed
importance medium
** Changed in: lxc (Ubuntu)
Importance: Undecided => Medium
** Changed in: lxc (Ubuntu)
Status: New =>
Ok, so this is working as expected. But I guess there is really zero
advantage to having a copy-clone on btrfs, so I think it's worth
changing.
status confirmed
importance medium
** Changed in: lxc (Ubuntu)
Importance: Undecided => Medium
** Changed in: lxc (Ubuntu)
Status: New =>
** Also affects: libvirt (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Vivid)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
*** This bug is a duplicate of bug 1524737 ***
https://bugs.launchpad.net/bugs/1524737
** This bug has been marked a duplicate of bug 1524737
systemd presents hugetblfs at /dev/hugepages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi,
Looking through the history of bug 1432644, AFAICS it was never "fixed",
it was worked around.
Ceph was built without support for lttng. The libvirt patch was only to
*silence* the denial for attempted access to lttng, not to grant the
access.
Are you asking only to update the explit
Thanks for submitting this bug. The fix is being pushed in the next
version.
** Changed in: libvirt (Ubuntu)
Importance: Undecided => Medium
** Changed in: libvirt (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: libvirt (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1531833
Title:
package libvirt-bin 1.2.16-2ubuntu11.15.10.1 failed to
Thanks.
This patch is in xenial's source. I'll mark this to be SRUd to wily.
** Also affects: libvirt (Ubuntu Wily)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: libvirt (Ubuntu Wily)
Importance:
Thanks.
This patch is in xenial's source. I'll mark this to be SRUd to wily.
** Also affects: libvirt (Ubuntu Wily)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: libvirt (Ubuntu Wily)
Importance:
The patch to fix this should be 91fdcefa7f145c1c39acc8e9a44fbfbf11568e54
upstream. It is in the xenial package. So I'm marking this fix
released and SRUing for wily.
Do we need this SRU'd to trusty too?
** Also affects: libvirt (Ubuntu Wily)
Importance: Undecided
Status: New
**
What were the fds? (ls -l)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532314
Title:
Buffer overflow in cgmanager
To manage notifications about this bug go to:
What were the fds? (ls -l)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1532314
Title:
Buffer overflow in cgmanager
To manage notifications about this bug go to:
The patch to fix this should be 91fdcefa7f145c1c39acc8e9a44fbfbf11568e54
upstream. It is in the xenial package. So I'm marking this fix
released and SRUing for wily.
Do we need this SRU'd to trusty too?
** Also affects: libvirt (Ubuntu Wily)
Importance: Undecided
Status: New
**
*** This bug is a duplicate of bug 1524737 ***
https://bugs.launchpad.net/bugs/1524737
** This bug has been marked a duplicate of bug 1524737
systemd presents hugetblfs at /dev/hugepages
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Also affects: libvirt (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Vivid)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@rahul
ping?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1393842
Title:
libvirt does not grant qemu-guest-agent channel perms
To manage notifications about this bug go to:
Hi,
could you please show the output of both:
sudo journalctl -xe
and
sudo systemctl status libvirt-bin.service -l
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1531833
Title:
package
Thanks - I'll push that fix to xenial and SRU to wily.
Where else do you need it?
** Changed in: libvirt (Ubuntu)
Importance: Undecided => High
** Changed in: libvirt (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs,
If you do
lxc-clone -s -o adt-xenial -n x1
does that snapshot the way you want?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532125
Title:
lxc-clone: Use btrfs backing store if original
If you do
lxc-clone -s -o adt-xenial -n x1
does that snapshot the way you want?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1532125
Title:
lxc-clone: Use btrfs backing store if
Blueprint changed by Serge Hallyn:
Work items changed:
Work items for ubuntu-15.11:
- [serge-hallyn] etckeeper: TODO
+ [serge-hallyn] etckeeper: DONE
[paelzer] NIS merge: DONE
Work items for ubuntu-15.12:
[raharper] : tgt merge (bug 1524982): DONE
[racb] nagios-plugins/monitoring
Hm, sadly the trace isn't very informative:
Core was generated by `/sbin/cgmanager -m name=systemd'.
Program terminated with signal SIGABRT, Aborted.
#0 0x7fade2d7a267 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:55
55 ../sysdeps/unix/sysv/linux/raise.c: No
Hm, sadly the trace isn't very informative:
Core was generated by `/sbin/cgmanager -m name=systemd'.
Program terminated with signal SIGABRT, Aborted.
#0 0x7fade2d7a267 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:55
55 ../sysdeps/unix/sysv/linux/raise.c: No
Ok, I see. At one point we had a special case to allow the overlay code
to write trusted.* xattrs for creating whiteouts.
However that is gone. Therefore when overlayfs v1 (mount -t overlayfs)
is mounted, root in a user namespace also is not able to rm a file which
exists in the lower fs.
Some
The type of the underlaying file does not matter, only the type of the
replacing object.
So if you
touch $t/dev; rm $t/dev; touch $t/dev
mkdir $t/dev; rmdir $t/ev; touch $t/dev
those succeed, while
touch $t/dev; rm $t/dev; mkdir $t/dev
mkdir $t/dev; rm $t/dev; mkdir $t/dev
both fail.
--
In ovl_create_over_whiteout(), the ovl_set_opaque() in the S_ISDIR()
block failed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1531747
Title:
overlay: mkdir fails if directory exists in lowerdir
Should also need fix in trusty-backports
The fix will come in 1.1.6.
** Also affects: lxc (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: lxc (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: lxc (Ubuntu Vivid)
Importance: Undecided
Should also need fix in trusty-backports
The fix will come in 1.1.6.
** Also affects: lxc (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: lxc (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: lxc (Ubuntu Vivid)
Importance: Undecided
This was fixed by commit 5eea90e8505d9f336bb28379d8575be159fdd2e1, it
was github issue http://github.com/lxc/lxc/issues/694.
It needs to be SRUd somewhat urgently.
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
This was fixed by commit 5eea90e8505d9f336bb28379d8575be159fdd2e1, it
was github issue http://github.com/lxc/lxc/issues/694.
It needs to be SRUd somewhat urgently.
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
Public bug reported:
If a directory exists in the lowerdir but not in the mounted
overlay, then mkdir of the directory in the target dir results
in a mysterious -EPERM. I've seen this both in wily kernel
(4.2.0-22-generic #27-Ubuntu) and in a hand-built xenial
master-next (with unrelated patches
summary overlay: mkdir in user namespace fails if directory exists in
lowerdir"
** Description changed:
If a directory exists in the lowerdir but not in the mounted
overlay, then mkdir of the directory in the target dir results
in a mysterious -EPERM. I've seen this both in wily kernel
I failed to reproduce the original problem, but the -proposed packages
pass the qa regression tests in lp:qa-regression-tests.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Quoting Joseph Salisbury (joseph.salisb...@canonical.com):
> Can you see if this bug also happens with the latest mainline kernel? It can
> be downloaded from:
That is not an option, because the mainline kernel doesn't support unprivileged
overlayfs mounting which is where this happens.
--
Quoting RussianNeuroMancer (1529...@bugs.launchpad.net):
> I have systemd installed.
> I mean, I can add systemd package as affected package again?
Yes I think that's fair, though it's more likely a bug in libvirt's
use of systemd-machined.
--
You received this bug notification because you are
Gah. Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1531191
Title:
qemu-kvm-init script called with undefined $KVM_HUGEPAGES
To manage notifications about this bug go to:
Gah. Thank you.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1531191
Title:
qemu-kvm-init script called with undefined $KVM_HUGEPAGES
To manage notifications about this bug go to:
801 - 900 of 15549 matches
Mail list logo
