So the problem is indeed that the cgroups are deleted using the
cgroupfs, and fuse doesn't get that information. The fuse kernel module
is caching the information for one second before re-querying userspace.
I've pushed a patch to lxcfs to drop the caching to a half second. I'm
posting a patch t
Actually that might not help. If the cgroup really did still exist,
then lxc would have refused to re-use it. I.e .instead of /lxc/x1, it
would then use /lxc/x1-1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Yup, just making lxc sleep 2 seconds works. So this is purely a race.
I'll fix it by having lxc excplicitly wait until the cgroups are removed
before re-execing after reboot.
** Changed in: lxc (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are
What does
sudo /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop
sudo /usr/lib/x86_64-linux-gnu/lxc/lxc-net start
sudo netstat -lap| grep LISTEN
show now that you've updated bind9's configuration?
** This bug is no longer a duplicate of bug 1240757
Bridge not created if bind
I believe what's happening is that systemd tries to mkdir init.scope
before the directory has been deleted and gets -EEXIST; then the kernel
finishes deleting it, then systemd tries to move itself to it but it is
gone.
Waiting for one more debugging build to verify.
--
You received this bug not
With cgfs i actually wasn't able to start the container in the first
place. I've now fixed at least that.
it wasn't the mkdir which was failing, but the subsequent attempt to
attach itself to it. That's because while cgmanager used to chown the
child files after creating a directory for us, cgfs
That was a red herring, actually. The cause of failure appears to be
the next line.
After fixing that so that the mkdir succeeds, it still fails on
Failed to allocate manager object: No such file or directory
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Doh', it's because I had a total brainfart while writing that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1514690
Title:
rebooting container with systemd >= 226 fails to create /lxc/adt-
xenial
When I test this using cgfs-backed lxcfs, the mkdir of init.cgroup fails after
setresuid(10, 10, 0).
This is odd since doing it manually using sudo -u \#10 -g \#10 mkdir
/sys/fs/cgroup/systemd/lxc/x1/x works fine.
--
You received this bug notification because you are a member of
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) => Serge Hallyn (serge-hallyn)
** Changed in: lxc (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
The download template (which is recommended) installs no ssh and no
ubuntu password.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1514080
Title:
lxc-templates lacks template for ubuntu core
To man
@oleg,
yes, but it is not an lxc bug, there's nothing lxc can do about it.
Stéphane un-marked it from lxc to make the lxc bug view more usable so
we can use it rather than ignore it :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
@arges,
did you want to push this patch into our package until it hits upstream?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501651
Title:
ARM chroot issues: fatal error: rt_sigaction failure
T
*** This bug is a duplicate of bug 1240757 ***
https://bugs.launchpad.net/bugs/1240757
Quoting Kevin Dalley (1452...@bugs.launchpad.net):
> *** This bug is a duplicate of bug 1240757 ***
> https://bugs.launchpad.net/bugs/1240757
>
> I have now added
>
> listen-on-v6 { none; };
> re
Hi Martin,
thanks for that info. During a reboot, lxc deletes the container's
cgroup, then recreates it. Is systemd expecting the cgroup it
previously created to stick around?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Can you show which libvirt version you are using?
Can you show the results of:
ls -l /etc/apparmor.d/libvirt
ls -l /proc /proc/self /proc/self/attr
And then the following manual test:
cd /tmp
cat > testprofile << EOF
profile i_cant_be_trusted_anymore {
/etc/ld.so.cache
Is that really the only strace output you saw?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1513367
Title:
qemu-system-x86_64/kvm-spice failed to boot a vm with appmor enabled
To manage notificati
*** This bug is a duplicate of bug 1240757 ***
https://bugs.launchpad.net/bugs/1240757
D'oh! thanks for that info. You are running bind9, which is causing
the conflict. To work around this, you can tell bind9 to not listen
on 10.0.3.1 - see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug
*** This bug is a duplicate of bug 1240757 ***
https://bugs.launchpad.net/bugs/1240757
** This bug is no longer a duplicate of bug 1452601
vivid container's networking.service fails on boot with signal=PIPE
** This bug has been marked a duplicate of bug 1240757
Bridge not created if bind
*** This bug is a duplicate of bug 1240757 ***
https://bugs.launchpad.net/bugs/1240757
** This bug is no longer a duplicate of bug 1452601
vivid container's networking.service fails on boot with signal=PIPE
** This bug has been marked a duplicate of bug 1240757
Bridge not created if bind
Right, this is mentioned in the manpage. You can force environment
to be cleared by passing --clear-env. Actually setting HOME to what
a login shell would do would require lxc-attach to make assumptions
about the container. However you can
lxc-attach -n trusty-vimprobable --clear-env -- su - ro
You're still getting
dnsmasq: failed to create listening socket for 10.0.3.1: Cannot
assign requested address
What does
sudo netstat -lap| grep LISTEN
show?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
** Description changed:
=
Bugs are not infrequently reported along the lines of
Unable to set Apparmor Profile for [emulator]: No such file or directory
- It is frequently (always?) the result of some value - a cdrom or disk
- file, smbios,
Thanks for that. I'm going to retitle this bug for the general topic
of properly reporting spaces in valius.
** Summary changed:
- Unable to set AppArmor profile for /usr/bin/kvm-spice
+ Unable to set AppArmor profile [...] no such file or directory
** Changed in: libvirt (Ubuntu)
Importan
Actually it seems reasonably likely that your problem is with:
-smbios type=1,manufacturer=OpenStack Foundation,product=OpenStack
Nova,version=12.0.0,serial=e87d7510-5766-e35e-8016-ebeb55d7deff,uuid=3dceb341
-643d-492a-8a47-8154da341c02,family=Virtual Machine
because the smbios has spaces in the
I believe the 'no such file or directory' is what qemu is reporting
about some device which openstack is trying to hand it.
Can you confirm that
/dev/hugepages/libvirt/qemu
exists (ls -l /dev/hugepages/libvirt)?
Try the following on your compute node to get strace output:
mv /usr/bin/qemu-syst
Ok, so the error msg is simply misleading - it says 'permission denied',
but the bridge does not exist.
Can you please show:
sudo /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop
sudo /usr/lib/x86_64-linux-gnu/lxc/lxc-net start
sudo brctl show
and see if your container now starts?
Please also paste /
** This bug is no longer a duplicate of bug 1512749
lxcbr0 dissappears on Ubuntu 15.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505576
Title:
internal error: Failed to initialize a valid fi
*** This bug is a duplicate of bug 1512749 ***
https://bugs.launchpad.net/bugs/1512749
Because AIUI the upgrade will install the fix but not restart network
manager.
** This bug has been marked a duplicate of bug 1512749
lxcbr0 dissappears on Ubuntu 15.10
--
You received this bug notific
please let us know if updating (and then perhaps rebooting) fixes it for
good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505576
Title:
internal error: Failed to initialize a valid firewall back
I suspect this is a duplicate of bug 1512749
Are you using network-manager?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505576
Title:
internal error: Failed to initialize a valid firewall backen
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
** 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.
+ Regressio
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 networking.ser
** 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
** 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 becau
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
Architecture: all
Source: vm-builder
Version: 0.12.4
Ok. It was 'fix released' in cgmanager and lxc by working around it (not
enabling threading). It is invalid in lxcfs in xenial because we have
switched to glib and gdbus there. The libnih and dbus bugs are still open,
though in dbus it is wontfix from upstream. Since dbus is wontfix, I think we
Hi,
The fix was uploaded last week for acceptance by the SRU team. It's
waiting to be accepted into -proposed. Then it will need to be tested
to be accepted into -updates.
https://launchpad.net/ubuntu/precise/+queue?queue_state=1&queue_text=lxc
--
You received this bug notification because yo
Hi,
you're actually geting EPERM, which means lxcbr0 exists. Please show
the output of:
sudo lxc-start -n escale_build -F -l trace -o /dev/stdout
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
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 subsc
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.
https://bugs.launchpad.net/bu
(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 f
** 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
@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.
https://bugs.launchpad.ne
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 into
** 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 notifica
*** 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 becau
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 installatioi
(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 abou
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)
Status:
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 l
** 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.
https://bug
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 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)
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.
** A
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:
packag
(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 install/u
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 (Ubu
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: virt-man
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.
https://bugs.lau
** 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 disa
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':
inte
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
@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 'qemu:///
@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
(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 Ubuntu
** 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
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"
name="/home/lxcunpriv/.local/share/lxc/c1/rootfs/dev/consol
** 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
Bugs
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 manag
** 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 o
** 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.
https://bugs.launchp
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.
https://bugs.launchpad.net/bugs/151
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.
h
*** 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
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 t
** 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.
https://bugs.launchpad.net/
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 subscrib
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, w
@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
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 `./u
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
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:
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 must
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 debdiff+pull-requ
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
ExecStart=/usr
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 right.
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
Ah, thanks for that info.
** Changed in: lxc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1508577
Title:
[wily] installing juju-local on ARM64 failed. bro
That seems like an unrelated bug. Please open a new bug, giving as much
information as possible about the two hosts and the vms.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1291321
Title:
migrati
Thanks! In that case that should be fixed as soon as we sync the new
0.2.8-1 from unstable into x. Then we can sru the patch itself.
** Also affects: virt-manager (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: netcf (Ubuntu Xenial)
Importance: Undecided
I don't see where anyone has identified what patches actually fixed
this, and no obvious message in git log , so offhand I'd say chances are
slim. Could you use the cloud archive, which should have the newer
versions?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Patch added: "And one more to fix in vms"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+attachment/4503681/+files/lxcneta.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509
Handle one more corner case
** Patch added: "lxcnet9.debdiff"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+attachment/4503630/+files/lxcnet9.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Final proposed patch for now. Uploaded to ppa:serge-hallyn/lxc-natty
for wily.
Installing this on a fresh ubuntu-cloud wily container (i.e. a broken
one) results in working lxcbr0 on new subnet.
** Patch added: "lxcnet8.debdiff"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+att
new patch.
It upgrades a broken container fine, but lxc-net is not properly started
until I manually call
/usr/lib/x86_64-linux-gnu/lxc/lxc-net stop
/usr/lib/x86_64-linux-gnu/lxc/lxc-net start
or reboot
** Patch added: "lxcnet6.debdiff"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/15
Updated debdiff, which
1. stops creation of /etc/default/lxc-net on package install
2. removes that file only if upgrading from the 1.0.4ubuntu4 version with an
umodified /etc/default/lxc-net file
** Patch added: "lxcnet4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+
I don't like disabling lxc-net, because it's simpler to tell a user to
apt-get install lxd
than to
systemctl enable lxc-net
or
echo "USE_LXC_BRIDGE=true" | sudo tee -a /etc/default/lxc-net
systemctl restart lxc-net
--
You received this bug notification because you are a member of Ubuntu
Bugs
801 - 900 of 9529 matches
Mail list logo
