[Bug 1569064] Re: ifupdown wants to configure interfaces it shouldn't (lxdbr0 or veth)
** Summary changed: - ifupdown wants to configure interfaces it shouldn't (lxdbr0) + ifupdown wants to configure interfaces it shouldn't (lxdbr0 or veth) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1569064 Title: ifupdown wants to configure interfaces it shouldn't (lxdbr0 or veth) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1569064/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1569064] Re: ifupdown wants to configure interfaces it shouldn't (lxdbr0)
ok. So under bug 1569974 i fixed cloud-init to not consider the bridge as something it should pick as a fallback nic. However, there is still a problem in that cloud-init may select the host side of a veth device. The result is that $ cat /etc/network/interfaces.d/50-cloud-init.cfg auto vethVH9WCK iface vethVH9WCK inet dhcp So a.) cloud-init needs to find some way to still do the right thing and pick the right nic ignoring those veth devices Note, though in a container eth0 (a veth) *is* the right device. b.) lxd should probably not bring up bridges or do other things before 'network-pre.target' cloud-init-local, the code that determines this runs: 'Before=network-pre.target' The fact taht it finds vethVH9WCK means that lxd ran that early. It probably means that lxd started containers that early, which is probably wrong as those containers might well expect to reach the interwebs during boot, and they will not be able to. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1569064 Title: ifupdown wants to configure interfaces it shouldn't (lxdbr0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1569064/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1569064] Re: ifupdown wants to configure interfaces it shouldn't (lxdbr0)
** This bug is no longer a duplicate of bug 1569974 networking fallback should ignore bridges ** Changed in: lxd (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1569064 Title: ifupdown wants to configure interfaces it shouldn't (lxdbr0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1569064/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1515278] Re: [SRU] rabbit queues should expire when unused
Hi Chris and James, python-oslo.messaging 2.5.0-1ubuntu2 has been verified on wily-proposed and trusty-liberty-proposed. Thanks, Corey ** Tags removed: verification-liberty-needed verification-needed ** Tags added: verification-done verification-liberty-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-oslo.messaging in Ubuntu. https://bugs.launchpad.net/bugs/1515278 Title: [SRU] rabbit queues should expire when unused To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1515278/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1521958] Re: rabbit: starvation of connections for reply
Hi Chris and James, python-oslo.messaging 2.5.0-1ubuntu2 has been verified on wily-proposed and trusty-liberty-proposed. Thanks, Corey ** Tags removed: verification-liberty-needed verification-needed ** Tags added: verification-done verification-liberty-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-oslo.messaging in Ubuntu. https://bugs.launchpad.net/bugs/1521958 Title: rabbit: starvation of connections for reply To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1521958/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1570119] Re: xenial ppc64le cloud image crashes on nested virt
** Also affects: qemu (Ubuntu) Importance: Undecided Status: New -- 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/1570119 Title: xenial ppc64le cloud image crashes on nested virt To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1570119/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1570142] Re: net-interface-handler needs updating for newer ifupdown
At this point, I think the second patch there is doing the right thing. The reason I asked slangasek to NAC my upload was that poweroff wasnt' working correctly. The reason poweroff wasn't working correctly was that cloud-init is writing 'auto eth0' where cloud-initramfs-dyn-netconf is writing 'manual eth0'. cloud-init's version means that ifupdown tries to bring the device down on shutdown. ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Also affects: cloud-init Importance: Undecided Status: New ** Also affects: maas-images Importance: Undecided Status: New ** Changed in: cloud-init Status: New => Confirmed ** Changed in: maas-images Status: New => Confirmed ** Changed in: cloud-init (Ubuntu) Status: New => Confirmed ** Description changed: newer ifupdown versions (those in xenial) now keep interface state in /run/network/ifstate. rather than combined in /run/network/ifstate . We need to update /lib/open-iscsi/net-interface-handler to write the interface name into /run/network/ifstate. and then also tear that down on down. The failure can be seen when booting a maas image, if you first move the included symlink out of the way: - p="/etc/network/interfaces"; - [ -e "$p.link" -o -L "$p.link" ] || mv "$p" "$p.link"; cp "$p.dist" "$p" + p="/etc/network/interfaces"; + [ -e "$p.link" -o -L "$p.link" ] || mv "$p" "$p.link"; cp "$p.dist" "$p" (maas images ship with /etc/network/interfaces as a symlink to ../../run/network/dynamic-interfaces and /run/network/dynamic-interfaces is populated by cloud-initramfs-dyn-netconf). + + This affects: + * cloud-init: cloud-init's fallback config currently writes 'auto' for the network device. the cloud-initramfs-dyn-netconf writes 'manual', and so ifupdown doesn't try to bring up *or* down the device. + * maas-images: the single difference from filesystem viewpoint from xenial lxd image to maas image is 'ln -snf ../../run/dynamic-interfaces /etc/network/interfaces' + * open-iscsi: the real need for open-iscsi's udev integration is to get the resolvconf updates applied. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: open-iscsi 2.0.873+git0.3b4b4500-14ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Wed Apr 13 23:58:27 2016 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) + TERM=xterm-256color + PATH=(custom, no user) SourcePackage: open-iscsi UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1570142 Title: net-interface-handler needs updating for newer ifupdown To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1570142/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1569064] Re: ifupdown wants to configure interfaces it shouldn't (lxdbr0)
*** This bug is a duplicate of bug 1569974 *** https://bugs.launchpad.net/bugs/1569974 ** This bug has been marked a duplicate of bug 1569974 networking fallback should ignore bridges -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1569064 Title: ifupdown wants to configure interfaces it shouldn't (lxdbr0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1569064/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
