Thanks, what about
sudo brctl show
sudo ifconfig -a
sudo journalctl -u lxc-net
sudo systemd-detect-virt
--
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/1452601
Title:
vivid container's
Thanks, what about
sudo brctl show
sudo ifconfig -a
sudo journalctl -u lxc-net
sudo systemd-detect-virt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452601
Title:
vivid container's
Hi,
I'd really prefer to avoid the potential breakage by trying to backport
this with 2months left to EOL. So I'm going to mark this wontfix for
vivid. If you reall need this, please reply here. Please remember you
can work around this by using upstart, or you can upgrade to wily which
has the
Hi,
I'd really prefer to avoid the potential breakage by trying to backport
this with 2months left to EOL. So I'm going to mark this wontfix for
vivid. If you reall need this, please reply here. Please remember you
can work around this by using upstart, or you can upgrade to wily which
has the
** Also affects: libvirt (Ubuntu Trusty)
Importance: Undecided
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
Actually, it seems that python-vm-builder *is* available in wily on
power8.
ubuntu@diamond:~$ apt-cache show python-vm-builder
Package: python-vm-builder
Priority: extra
Section: universe/utils
Installed-Size: 4248
Maintainer: Serge Hallyn <serge.hal...@ubuntu.com>
Architecture: all
Sour
** Description changed:
+ =
+ SRU Justification
+ Impact: cannot start vms on nfs mounted disk images
+ Testcase: set up libvirt managed nfs mount, try to start a vm on it.
+ Fix: add 'network ipv6' permission to virt-aa-helper's apparmor policy.
+
Actually, it seems that python-vm-builder *is* available in wily on
power8.
ubuntu@diamond:~$ apt-cache show python-vm-builder
Package: python-vm-builder
Priority: extra
Section: universe/utils
Installed-Size: 4248
Maintainer: Serge Hallyn <serge.hal...@ubuntu.com>
Architecture: all
Sour
** Also affects: libvirt (Ubuntu Trusty)
Importance: Undecided
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
** Changed in: libvirt (Ubuntu)
Importance: Undecided => High
** Changed in: libvirt (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: libvirt (Ubuntu Vivid)
Importance: Undecided => High
** Changed in: libvirt (Ubuntu Wily)
Importance: Undecided => High
--
You received
** Changed in: vm-builder (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/235562
Title:
Add ability to build Debian virtual
** Changed in: vm-builder (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/235562
Title:
Add ability to build Debian virtual machines
To manage
Yup, we need
https://github.com/lxc/lxc/commit/f348e47c93568b4f0c371cf5df1c98d4e816a86c
in the packages.
--
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/1497420
Title:
systemd 226
Yup, we need
https://github.com/lxc/lxc/commit/f348e47c93568b4f0c371cf5df1c98d4e816a86c
in the packages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1497420
Title:
systemd 226 (moving pid 1
@Kevin,
could you please give some more details? In particular, release of both
host and container, where exactly it fails, and the relevant journalctl
output.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Kevin,
could you please give some more details? In particular, release of both
host and container, where exactly it fails, and the relevant journalctl
output.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** Changed in: shadow (Ubuntu Vivid)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1475749
Title:
usermod --add-subuids fails for users not in /etc/passwd
(sorry, i msread the bug history)
** Changed in: shadow (Ubuntu Vivid)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1475749
Title:
usermod --add-subuids
The test case in the Description passed cleanly for me (and failed
without -proposed)
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I don't know. libnih is still a nice library and it would be nice if it could
be fixed. Certainly the lxcfs bug should be marked invalid since we no longer
use it. Perhaps lxc eventually, but not yet.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
I don't know. libnih is still a nice library and it would be nice if it could
be fixed. Certainly the lxcfs bug should be marked invalid since we no longer
use it. Perhaps lxc eventually, but not yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for reporting this bug.
Can you show the xml for the libvirt managed nfs storage and for the VM?
The virt-aa-helper policy has
# needed for when disk is on a network filesystem
network inet,
Which I suspect should prevent this from happening, so I will target
this at apparmor.
**
Thanks for reporting this bug.
Can you show the xml for the libvirt managed nfs storage and for the VM?
The virt-aa-helper policy has
# needed for when disk is on a network filesystem
network inet,
Which I suspect should prevent this from happening, so I will target
this at apparmor.
**
Oct 31 18:12:17 majid-top lxc-net[6891]: iptables v1.4.21: can't initialize
iptables table `nat': Table does not exist (do you need to insmod?)
Oct 31 18:12:17 majid-top lxc-net[6891]: Perhaps iptables or your kernel needs
to be upgraded.
Oct 31 18:12:17 majid-top lxc-net[6891]: Failed to setup
** Attachment added: "/var/log/dist-upgrade/apt.log file"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1511875/+attachment/4511345/+files/apt.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This appears to be fixed now in xenial. I think a simple no-change
rebuild in any release will enable it in power8. Please comment here
with any release where you do need it.
** Changed in: vm-builder (Ubuntu)
Importance: Undecided => Medium
** Changed in: vm-builder (Ubuntu)
*** This bug is a duplicate of bug 1004606 ***
https://bugs.launchpad.net/bugs/1004606
** This bug has been marked a duplicate of bug 1004606
virsh create-snapshot fails to create external snapshot
(blockdev-snapshot-sync fails in json monitor)
--
You received this bug notification
It does this in an unprivileged (true root) as well as a apparmor-
unconfined container.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511875
Title:
Can't upgrade from 15.10 Wily to 16.04 Xenial
(marking 'invalid' meaning 'cannot reproduce any more')
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506378
Title:
libvirt-bin configuration after installatioin fails
To manage notifications
Thanks for the update.
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506378
Title:
libvirt-bin configuration after
Thanks for the update.
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Invalid
--
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/1506378
Title:
libvirt-bin configuration
Oct 31 18:12:17 majid-top lxc-net[6891]: iptables v1.4.21: can't initialize
iptables table `nat': Table does not exist (do you need to insmod?)
Oct 31 18:12:17 majid-top lxc-net[6891]: Perhaps iptables or your kernel needs
to be upgraded.
Oct 31 18:12:17 majid-top lxc-net[6891]: Failed to setup
This appears to be fixed now in xenial. I think a simple no-change
rebuild in any release will enable it in power8. Please comment here
with any release where you do need it.
** Changed in: vm-builder (Ubuntu)
Importance: Undecided => Medium
** Changed in: vm-builder (Ubuntu)
** Attachment added: "/var/log/dist-upgrade/apt.log file"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1511875/+attachment/4511345/+files/apt.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in
same thing happens with vivid->wily upgrade.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Confirmed
** Changed in: lxc (Ubuntu)
Status: New => Triaged
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntu-release-upgrader (Ubuntu)
same thing happens with vivid->wily upgrade.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Confirmed
** Changed in: lxc (Ubuntu)
Status: New => Triaged
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntu-release-upgrader (Ubuntu)
It does this in an unprivileged (true root) as well as a apparmor-
unconfined container.
--
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/1511875
Title:
Can't upgrade from 15.10 Wily to
Actually the most telling sign in the logs here is
Oct 09 11:56:42 quelbo lxc-net[23366]: lxc-net is already running
If someone can reproduce this again, please attach the same information
Nick had assigned in addition to 'ifconfig -a' and 'systemctl -u lxc-
net' output.
** Changed in: lxc
(marking incomplete as we need more information to debug, but we've lost
the reproducer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1504496
Title:
package lxc 1.1.4-0ubuntu0.1 failed to
fwiw i don't think this is bug 1490110 because the signature is
different - there is complaint about the sysv job not being there.
--
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/1504496
Actually the most telling sign in the logs here is
Oct 09 11:56:42 quelbo lxc-net[23366]: lxc-net is already running
If someone can reproduce this again, please attach the same information
Nick had assigned in addition to 'ifconfig -a' and 'systemctl -u lxc-
net' output.
** Changed in: lxc
(marking incomplete as we need more information to debug, but we've lost
the reproducer)
--
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/1504496
Title:
package lxc 1.1.4-0ubuntu0.1
fwiw i don't think this is bug 1490110 because the signature is
different - there is complaint about the sysv job not being there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1504496
Title:
** Changed in: vm-builder (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/517067
Title:
Using virtio for block devices makes disks and partitions
** Changed in: vm-builder (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/517067
Title:
Using virtio for block devices makes
Ok, thanks. so ncftool dumpxml actually stil works, but
virsh iface-dumpxml fails. It is fixed in x (i can now test
that :), so we just need to SRU that patch to t,v,w.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to netcf in Ubuntu.
Ok, thanks. so ncftool dumpxml actually stil works, but
virsh iface-dumpxml fails. It is fixed in x (i can now test
that :), so we just need to SRU that patch to t,v,w.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Actually trusty is not affected
** Also affects: virt-manager (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: netcf (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: netcf (Ubuntu Vivid)
Importance: Undecided => High
** Changed in:
Actually trusty is not affected
** Also affects: virt-manager (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: netcf (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: netcf (Ubuntu Vivid)
Importance: Undecided => High
** Changed in:
@ferdez,
are you able to provide the information requested in comment #7?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to netcf in Ubuntu.
https://bugs.launchpad.net/bugs/1481295
Title:
virt-manager after upgrade: Error polling
@ferdez,
are you able to provide the information requested in comment #7?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481295
Title:
virt-manager after upgrade: Error polling connection
@xianghui,
will you be able to provide the information requested in comment #19?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384532
Title:
Unable to set AppArmor profile for /usr/bin/kvm-spice
Quoting Stewart Smith (stew...@linux.vnet.ibm.com):
> Serge Hallyn <1510...@bugs.launchpad.net> writes:
> > Which package are you trying to use?
>
> gitian-builder - an attempt to work on repeatable builds for OpenPower
> firmware (and having it all run on ppc64el rat
D'oh, that makes sense. I'll try again with that - thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to netcf in Ubuntu.
https://bugs.launchpad.net/bugs/1481295
Title:
virt-manager after upgrade: Error polling connection
D'oh, that makes sense. I'll try again with that - thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481295
Title:
virt-manager after upgrade: Error polling connection 'qemu:///system':
Quoting Stewart Smith (stew...@linux.vnet.ibm.com):
> Serge Hallyn <1510...@bugs.launchpad.net> writes:
> > Which package are you trying to use?
>
> gitian-builder - an attempt to work on repeatable builds for OpenPower
> firmware (and having it all run on ppc64el rat
Ok, I just built a package on power8 switching Architecture:all to any.
I don't see any reason not to push with that change. There are some
other changes in the bzr tree and one I'm still reviewing, I'll upload
to xenial in a bit.
I assume you'll need this SRU'd - which releases do you need this
Ok, I just built a package on power8 switching Architecture:all to any.
I don't see any reason not to push with that change. There are some
other changes in the bzr tree and one I'm still reviewing, I'll upload
to xenial in a bit.
I assume you'll need this SRU'd - which releases do you need this
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: lxc (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: lxc (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: lxc (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: lxc (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: lxc (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
** Also affects: lxc (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: lxc (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: lxc (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Which package are you trying to use?
We could change this for xenial (although a new attempt to drop
vm-builder fromthe archive would serve us better)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
** Description changed:
+ ==
+ SRU Justification:
+ Impact: containers fail to start!
+ Regression potential: we only add a copy of an existing apparmor allow rule
+ with a different syntax (no trailing /), leaving the old one for
** Description changed:
+ ==
+ SRU Justification:
+ Impact: containers fail to start!
+ Regression potential: we only add a copy of an existing apparmor allow rule
+ with a different syntax (no trailing /), leaving the old one for
Which package are you trying to use?
We could change this for xenial (although a new attempt to drop
vm-builder fromthe archive would serve us better)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yup, switching in the upstream fix works - will upload that in a bit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509752
Title:
Bug in ensure_not_symlink() from 0003-CVE-2015-1335.patch
To
Yup, switching in the upstream fix works - will upload that in a bit.
--
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/1509752
Title:
Bug in ensure_not_symlink() from
No, sadly one testcase - lxc-test-unpriv - still fails:
Oct 28 15:33:49 lxct1 kernel: [ 2659.417204] type=1400
audit(1446046429.177:52): apparmor="DENIED" operation="mount"
info="failed flags match" error=-13 profile="/usr/bin/lxc-start"
No, sadly one testcase - lxc-test-unpriv - still fails:
Oct 28 15:33:49 lxct1 kernel: [ 2659.417204] type=1400
audit(1446046429.177:52): apparmor="DENIED" operation="mount"
info="failed flags match" error=-13 profile="/usr/bin/lxc-start"
** Description changed:
- This bug/limitation is present in lxc from 1.0.7-0ubuntu0.5 through
- 1.0.7-0ubuntu0.9 (or anything that incorporates
- 0003-CVE-2015-1335.patch). Basically, the limitation is obvious when
- using recursive bind mounts because ensure_not_symlink() only checks the
- last
** Description changed:
- This bug/limitation is present in lxc from 1.0.7-0ubuntu0.5 through
- 1.0.7-0ubuntu0.9 (or anything that incorporates
- 0003-CVE-2015-1335.patch). Basically, the limitation is obvious when
- using recursive bind mounts because ensure_not_symlink() only checks the
- last
(invalid would probably be a better status for the development release,
but i dont' want to scare the SRU team :)
Uploaded a workaround for this bug. Using the upstream fix sadly is
still broken by apparmor+overlayfs bugs.
--
You received this bug notification because you are a member of
(invalid would probably be a better status for the development release,
but i dont' want to scare the SRU team :)
Uploaded a workaround for this bug. Using the upstream fix sadly is
still broken by apparmor+overlayfs bugs.
--
You received this bug notification because you are a member of
@stefan-huehner - sorry, I'm losing track. is what you are asking for
just a lxc update to precise-proposed with the new apparmor allow rule
that jj suggested?
If so, in comment #33 I was trying to encourage a debdiff to be posted
by someone who could best test it. I'll then sponsor it into the
Thanks, I've merged this upstream. I may push a new version to xenial
in a few days.
** Changed in: vmbuilder
Status: Invalid => Fix Released
** No longer affects: ubuntu-vm-builder (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: netcf (Ubuntu Xenial)
Status: Triaged => Fix Released
** Changed in: virt-manager (Ubuntu Xenial)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: netcf (Ubuntu Xenial)
Status: Triaged => Fix Released
** Changed in: virt-manager (Ubuntu Xenial)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to netcf in Ubuntu.
Thanks - haven't tested, but it certainly makes sense.
status: confirmed
importance: high
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Thanks - haven't tested, but it certainly makes sense.
status: confirmed
importance: high
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server
Thanks, I've merged this upstream. I may push a new version to xenial
in a few days.
** Changed in: vmbuilder
Status: Invalid => Fix Released
** No longer affects: ubuntu-vm-builder (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I'm trying to come up with a brief test case to SRU this to wily, but
i don't seem to get an error when I do:
sudo ifconfig eth0:0 192.168.99.1 up
sudo ncftool list
sudo ncftool dumpxml eth0:0
Or, at least, no different results than with the patch applied. Can you
show
ifconfig -a
output for
I'm trying to come up with a brief test case to SRU this to wily, but
i don't seem to get an error when I do:
sudo ifconfig eth0:0 192.168.99.1 up
sudo ncftool list
sudo ncftool dumpxml eth0:0
Or, at least, no different results than with the patch applied. Can you
show
ifconfig -a
output for
*** This bug is a duplicate of bug 1468611 ***
https://bugs.launchpad.net/bugs/1468611
@paugnu
which ubuntu release are you on and what is your dnsmasq version? (dpkg
-l dnsmasq) Do you have bind installed?
Does creating /etc/dnsmasq.conf fix without having to clear out
/etc/dnsmasq.d/lxc
*** This bug is a duplicate of bug 1468611 ***
https://bugs.launchpad.net/bugs/1468611
@paugnu
which ubuntu release are you on and what is your dnsmasq version? (dpkg
-l dnsmasq) Do you have bind installed?
Does creating /etc/dnsmasq.conf fix without having to clear out
/etc/dnsmasq.d/lxc
Apparently the kernel is now fixed so that we should be able to use the
upstream fix. I'm going to try to get that into the trusty package
rather than keep tweakng this separate patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Apparently the kernel is now fixed so that we should be able to use the
upstream fix. I'm going to try to get that into the trusty package
rather than keep tweakng this separate patch.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
@stefan-huehner - sorry, I'm losing track. is what you are asking for
just a lxc update to precise-proposed with the new apparmor allow rule
that jj suggested?
If so, in comment #33 I was trying to encourage a debdiff to be posted
by someone who could best test it. I'll then sponsor it into the
Hi,
so I'm getting the feeling that we ought to turn this bug into one for
enhancing the transparancy of errors. Too many errors are mis-reported
by this line.
For your particular case, could we try an experiment? Please install
strace on the compute host, and edit /usr/bin/kvm-spice to read:
It's the setuid and setgid bits with user namespace.
** 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/1498162
Title:
unable
You can work around this by doing
echo 0 | sudo tee -a /proc/sys/fs/protected_hardlinks
on the host.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1498162
Title:
unable to make backup link of
Quoting Stéphane Graber (stgra...@stgraber.org):
> I agree, the stage 2 fix for this issue concerns me with regard to
> regressing current use cases.
>
> As much as I'd like to get rid of the rest of this issue (any user of
> 10.0.4.0/24 behind a router looses connectivity to that subnet), we
Quoting Stéphane Graber (stgra...@stgraber.org):
> I agree, the stage 2 fix for this issue concerns me with regard to
> regressing current use cases.
>
> As much as I'd like to get rid of the rest of this issue (any user of
> 10.0.4.0/24 behind a router looses connectivity to that subnet), we
New image works for me in lxc:
lxcbr0Link encap:Ethernet HWaddr 76:79:3e:90:1c:88
inet addr:10.0.4.1 Bcast:0.0.0.0 Mask:255.255.255.0
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
New image works for me in lxc:
lxcbr0Link encap:Ethernet HWaddr 76:79:3e:90:1c:88
inet addr:10.0.4.1 Bcast:0.0.0.0 Mask:255.255.255.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509414
I was able to For stage two, at least with systemd, I changed
/lib/systemd/system/lxd-startup.service to:
[Unit]
Description=Container hypervisor based on LXC - boot time check
After=cgmanager.service lxd-unix.socket
Requires=cgmanager.service lxd-unix.socket
[Service]
Type=oneshot
I was able to For stage two, at least with systemd, I changed
/lib/systemd/system/lxd-startup.service to:
[Unit]
Description=Container hypervisor based on LXC - boot time check
After=cgmanager.service lxd-unix.socket
Requires=cgmanager.service lxd-unix.socket
[Service]
Type=oneshot
Quoting Joseph Bisch (josephbi...@gmail.com):
> I just tried filling out the contributor agreement (so far I am the sole
> author of the changes), but I'm not sure what to put for the project
> contact and it is required. Do I put you, Serge?
Uh, I'm really not sure. Putting me down sounds
Quoting Joseph Bisch (josephbi...@gmail.com):
> I just tried filling out the contributor agreement (so far I am the sole
> author of the changes), but I'm not sure what to put for the project
> contact and it is required. Do I put you, Serge?
Uh, I'm really not sure. Putting me down sounds
This lxc debdiff (not appropriate upstream lxc) and a pull request
against lxd-pkg-ubuntu (https://github.com/lxc/lxd-pkg-ubuntu/pull/7)
combined should implement stage 2 of the fix.
Note I've tested these when separately implemented by hand, but have not
built packages with this
1101 - 1200 of 15550 matches
Mail list logo
