[Bug 1333630] Re: screen caught signal 11 core dumped
I'm YET AGAIN having to build screen from source for a "SUPPORTED" distro. HEOO -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to screen in Ubuntu. https://bugs.launchpad.net/bugs/1333630 Title: screen caught signal 11 core dumped To manage notifications about this bug go to: https://bugs.launchpad.net/screen/+bug/1333630/+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 1503034] Re: Autofs 5.1.1-1ubuntu2 crashes with segfault on startup
Unfortunately I just rolled 20 servers to 15.10 and this bug bit me big time. Is there a workaround or estimate when complete or do I need to roll back to 15.04. Is it possible to just install the autofs from the 15.04 distro ? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in Ubuntu. https://bugs.launchpad.net/bugs/1503034 Title: Autofs 5.1.1-1ubuntu2 crashes with segfault on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1503034/+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 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers
Hello Mike, or anyone else affected, Accepted lxc into wily-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxc/1.1.4-0ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- 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/1509414 Title: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1508577] Re: [wily] installing juju-local on ARM64 failed. broken apt dependency
Ah, thanks for that info. ** Changed in: lxc (Ubuntu) Status: New => Incomplete -- 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/1508577 Title: [wily] installing juju-local on ARM64 failed. broken apt dependency To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1508577/+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 1509586] Re: SSLv3 enabled in apache2 by default
I don't think we will want to push updates to disable ssl3 on existing systems, and I'm not sure how feasible it would be to push an update that only modifies the defaults for brand-new installs. I suspect the only thing to be done for 14.04 LTS is to educate system administrators about the risks of ssl3 and how to disable it. We should certainly verify that ssl3 is disabled by default in xenial. Thanks ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1509586 Title: SSLv3 enabled in apache2 by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1509586/+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 1481295] Re: virt-manager after upgrade: Error polling connection 'qemu:///system': internal error: could not get interface XML description: File operation failed - Failed to read (null)
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 Status: New ** Also affects: virt-manager (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: netcf (Ubuntu Wily) Importance: Undecided Status: New ** Changed in: netcf (Ubuntu Wily) Status: New => Triaged ** Changed in: netcf (Ubuntu Xenial) Status: New => Triaged ** Changed in: virt-manager (Ubuntu Wily) Status: New => Triaged ** Changed in: virt-manager (Ubuntu Xenial) Status: New => Triaged ** Changed in: virt-manager (Ubuntu Xenial) Importance: Undecided => High ** Changed in: virt-manager (Ubuntu Wily) Importance: Undecided => High ** Changed in: netcf (Ubuntu Xenial) Importance: Undecided => High ** Changed in: netcf (Ubuntu Wily) Importance: Undecided => High -- 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 'qemu:///system': internal error: could not get interface XML description: File operation failed - Failed to read (null) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcf/+bug/1481295/+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
Re: [Bug 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty
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 Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1291321 Title: migration fails between 12.04 Precise and 14.04 Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1291321/+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 1457639] Re: qemu-img qcow2 conversion hangs on large core systems
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 Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1457639 Title: qemu-img qcow2 conversion hangs on large core systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1457639/+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 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers
** 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 Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1509414 Title: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1457639] Re: qemu-img qcow2 conversion hangs on large core systems
Any chance of having the fixes (or fixed version) backported to trusty? We need this for the HP Moonshot hardware we're using in ScalingStack and am currently working around it with a backport of the version in Vivid[1] [1]https://launchpad.net/~canonical-is-sa/+archive/ubuntu/arm64-infra- workarounds/+packages ** Also affects: qemu (Ubuntu Trusty) 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/1457639 Title: qemu-img qcow2 conversion hangs on large core systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1457639/+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 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers
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 Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1509414 Title: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers
** Changed in: lxc (Ubuntu) Assignee: (unassigned) => Stéphane Graber (stgraber) -- 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/1509414 Title: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1488815] Re: Kernel traces with skb_warn_bad_offload showing up during an AIO deployment on Ubuntu 14.04
** Changed in: openstack-ansible/trunk Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1488815 Title: Kernel traces with skb_warn_bad_offload showing up during an AIO deployment on Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-ansible/+bug/1488815/+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 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers
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/+attachment/4503564/+files/lxcnet8.debdiff -- 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/1509414 Title: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers
Action plan: Stage 1 - Configure lxc-net at boot rather than at install. * This addresses the network failure for 15.10 containers started on 15.10 hosts (patch above in comment #6) Stage 2 - Start lxc-net through systemd on the first launch of an LXC container. * This mitigates the unroutable 10.0.x.0/16 network issue for general cloud image users. With this step we’re back to Trusty function. * This will work for privileged users, like Juju, without any interaction. Unprivileged users will be directed to start the service on the first container launch. Next action: - serge-hallyn working on patch (last update in comment #7) and code in ppa:serge-hallyn/lxc-natty. Patch is not yet ready for upload and serge will update as he progresses. - Once ready, uploaded, and published in -proposed, email ring rcj/utlemming and we'll ensure cloud image builder picks this up ASAP to build -proposed images -- 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/1509414 Title: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers
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/1509414/+attachment/4503549/+files/lxcnet6.debdiff -- 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/1509414 Title: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers
** Summary changed: - lxc postinst script checks available interfaces, can choose + pre-installed lxc in cloud image produces broken lxc (and later lxd) containers ** Description changed: [Problem] The released wily image preinstalls lxc, which breaks the assumption that lxc's preinst packaging script makes: It inspects the network to try to pick a 10.0.N.0 network that isn't being used, with N starting at 3, so this appears to have picked 10.0.3.0 when it was installed on whatever system was generating the - image. This conflicts with the network that eth0 gets attached to when - the image is brought up in a container, because it gets attached to the - host's lxcbr0, which is using 10.0.3.x. + image. - This affects LXC, and should affect LXD but doesn't currently, as the metadata used for lxd images is still pointing to a beta2 release. - The easiest way to reproduce this is to use the ubuntu-cloud lxc template on a wily host: + When a container is started, it will dhcp on eth0 and get 10.0.3.X as + expected. The problem comes when the lxc-net service that is already + installed in that container starts and configures *its* lxcbr0 with + 10.0.3.X. The networking inside the container is broken at that point. + + This affects LXC containers, and should affect LXD containers but + doesn't currently, as the metadata used for lxd images is still pointing + to a beta2 release (bug 1509390). + + The easiest way to reproduce this is to use the ubuntu-cloud lxc + template on a wily host. [Test Case] 1.) Verify expectation for each image - -disk1.img cloud image, check for file - -root.tar.xz image (used by lxd) and check for file - -root.tar.gz image (used by lxc) For each of those images, verify: a.) A cloud image should not have /etc/default/lxc-net b.) lxd should be installed (dpkg-query --show | grep lxd) 2.) Start instance from updated image and start instance in lxc inside launch instance on openstack or kvm or other verify lxcbr0 bridge exists lxc-create -t ubuntu-cloud -n bugcheck -- --release=wily --stream=daily # wait until lxc-ls --fancy shows 'running' lxc-attach -n bugcheck wget http://ubuntu.com 3.) Start instance from updated image and start instance in lxd inside launch instance on openstack or kvm or other verify lxcbr0 bridge exists lxd import-images ubuntu wily lxc launch ubuntu # wait some amount lxc attach bugcheck wget http://ubuntu.com [Regression Potentional] The highest chance for fallout is a change in the /16 network that is chosen conflicting with some existing service. [Other Info] Default apt install of lxc has always picked some 10.0.X.0/16 network to use for its lxcbr0 bridge. That network (often 10.0.3.0/16) would then be unreachable from the host. The same behavior occurs with libvirt-bin and many other such services. We are moving that logic to happen the first time that 'lxc-net' service starts. This means first boot for a cloud instance rather than cloud-image build time. [Work around] To patch / fix an existing cloud image to make lxc and lxd guests start simply change the config of /etc/default/lxc-net to have something other than 10.0.3.0. - sudo sed -i '/^LXC.*10[.]0[.][0-9][.]/s/10.0.[0-9]./10.0.4./g' /etc/default/lxc-net && - sudo service lxc-net stop && - sudo service lxc-net start + sudo sed -i '/^LXC.*10[.]0[.][0-9][.]/s/10.0.[0-9]./10.0.4./g' /etc/default/lxc-net && + sudo service lxc-net stop && + sudo service lxc-net start -- 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/1509414 Title: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1437846] Re: akonadi mysql 5.6 crash with signal 11
I've had similar problems. It seems to me that the default Akonadi options for MySQL include a table_cache parameter, but it's been deprecated since 5.1 and in 5.6 prevents a start of the database. Removing this options did the trick for me. In MariaDB documentation there's a remark that "all versions of MariaDB are based on MySQL 5.1 and greater, thus the table_cache option is deprecated in favor of table_open_cache." -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1437846 Title: akonadi mysql 5.6 crash with signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1437846/+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 1509414] Re: lxc postinst script checks available interfaces, can choose
** Description changed: [Problem] The released wily image preinstalls lxc, which breaks the assumption that lxc's preinst packaging script makes: It inspects the network to try to pick a 10.0.N.0 network that isn't being used, with N starting at 3, so this appears to have picked 10.0.3.0 when it was installed on whatever system was generating the image. This conflicts with the network that eth0 gets attached to when the image is brought up in a container, because it gets attached to the host's lxcbr0, which is using 10.0.3.x. This affects LXC, and should affect LXD but doesn't currently, as the metadata used for lxd images is still pointing to a beta2 release. The easiest way to reproduce this is to use the ubuntu-cloud lxc template on a wily host: [Test Case] - sudo lxc-create -t ubuntu-cloud -n wily - sudo lxc-start -n wily - sudo lxc-attach -n wily - # inside container, test connectivity, eg: - apt-get update + 1.) Verify expectation for each image +- -disk1.img cloud image, check for file +- -root.tar.xz image (used by lxd) and check for file +- -root.tar.gz image (used by lxc) + +For each of those images, verify: +a.) A cloud image should not have /etc/default/lxc-net +b.) lxd should be installed (dpkg-query --show | grep lxd) + + 2.) Start instance from updated image and start instance in lxc inside +launch instance on openstack or kvm or other +verify lxcbr0 bridge exists +lxc-create -t ubuntu-cloud -n bugcheck -- --release=wily --stream=daily +# wait until lxc-ls --fancy shows 'running' +lxc-attach -n bugcheck wget http://ubuntu.com + + 3.) Start instance from updated image and start instance in lxd inside +launch instance on openstack or kvm or other +verify lxcbr0 bridge exists +lxd import-images ubuntu wily +lxc launch ubuntu +# wait some amount +lxc attach bugcheck wget http://ubuntu.com + [Regression Potentional] Currently none as networking didn't work initially. ** Description changed: [Problem] The released wily image preinstalls lxc, which breaks the assumption that lxc's preinst packaging script makes: It inspects the network to try to pick a 10.0.N.0 network that isn't being used, with N starting at 3, so this appears to have picked 10.0.3.0 when it was installed on whatever system was generating the image. This conflicts with the network that eth0 gets attached to when the image is brought up in a container, because it gets attached to the host's lxcbr0, which is using 10.0.3.x. This affects LXC, and should affect LXD but doesn't currently, as the metadata used for lxd images is still pointing to a beta2 release. The easiest way to reproduce this is to use the ubuntu-cloud lxc template on a wily host: [Test Case] 1.) Verify expectation for each image -- -disk1.img cloud image, check for file -- -root.tar.xz image (used by lxd) and check for file -- -root.tar.gz image (used by lxc) + - -disk1.img cloud image, check for file + - -root.tar.xz image (used by lxd) and check for file + - -root.tar.gz image (used by lxc) -For each of those images, verify: -a.) A cloud image should not have /etc/default/lxc-net -b.) lxd should be installed (dpkg-query --show | grep lxd) + For each of those images, verify: + a.) A cloud image should not have /etc/default/lxc-net + b.) lxd should be installed (dpkg-query --show | grep lxd) 2.) Start instance from updated image and start instance in lxc inside -launch instance on openstack or kvm or other -verify lxcbr0 bridge exists -lxc-create -t ubuntu-cloud -n bugcheck -- --release=wily --stream=daily -# wait until lxc-ls --fancy shows 'running' -lxc-attach -n bugcheck wget http://ubuntu.com + launch instance on openstack or kvm or other + verify lxcbr0 bridge exists + lxc-create -t ubuntu-cloud -n bugcheck -- --release=wily --stream=daily + # wait until lxc-ls --fancy shows 'running' + lxc-attach -n bugcheck wget http://ubuntu.com 3.) Start instance from updated image and start instance in lxd inside -launch instance on openstack or kvm or other -verify lxcbr0 bridge exists -lxd import-images ubuntu wily -lxc launch ubuntu -# wait some amount -lxc attach bugcheck wget http://ubuntu.com - + launch instance on openstack or kvm or other + verify lxcbr0 bridge exists + lxd import-images ubuntu wily + lxc launch ubuntu + # wait some amount + lxc attach bugcheck wget http://ubuntu.com [Regression Potentional] - Currently none as networking didn't work initially. + The highest chance for fallout is a change in the /16 network that is chosen conflicting with some existing service. + + [Other Info] + Default apt install of lxc has always picked some 10.0.X.0/16 network to use for its lxcbr0 bridge. That network (often 10.0.3.0/16) would then be unreachable from the host.
[Bug 1508577] Re: [wily] installing juju-local on ARM64 failed. broken apt dependency
fwiw, this isn't a general arm64 problem. I can install juju-local on a mustang running wily w/o a problem. I suspect it maybe due to using a custom kernel, possibly with some networking features disabled in the config. I've asked Manoj to set -x /usr/lib/aarch64-linux-gnu/lxc/lxc- net to see if that is the case. -- 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/1508577 Title: [wily] installing juju-local on ARM64 failed. broken apt dependency To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1508577/+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 1509414] Re: lxc postinst script checks available interfaces, can choose
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/+attachment/4503531/+files/lxcnet4.debdiff -- 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/1509414 Title: lxc postinst script checks available interfaces, can choose To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509422] Re: package uses versioned shebangs
** Also affects: python-os-testr (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-json-patch in Ubuntu. https://bugs.launchpad.net/bugs/1509422 Title: package uses versioned shebangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-bashate/+bug/1509422/+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 1509457] Re: SMBD User authentication doesn't work after dist upgrade to 15.10
I have the same issue amd64 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1509457 Title: SMBD User authentication doesn't work after dist upgrade to 15.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1509457/+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
Re: [Bug 1508225] Re: tipc tool isn't built in iproute2
Thank you for your quick response. However, the tag "wishlist" does not sound very convincing to me. TIPC is not a one-man or small interest group project, despite still being little known. It is the main IPC solution used by my company, telco vendor Ericsson, as well as by WindRiver, Huawei and numerous other big and small companies. It would be very nice (an I would personally be very pleased) if we could add Debian/Ubuntu to our list of eligible distros for our applications. Thank you Jon Maloy, Ericsson Canada, Montreal On 10/21/2015 04:16 AM, Robie Basak wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. > > I see that libmnl-dev is in universe in Ubuntu so it should be > relatively easy to add the build dependency, but we are in final freeze > right now so this may have to wait until the next release. > > This bug also should be sent upstream to Debian as our build-depends > line is derived from theirs, and I don't see any reason for Ubuntu to be > different from Debian here. > > ** Tags added: needs-upstream-report > > ** Changed in: iproute2 (Ubuntu) > Status: New => Triaged > > ** Changed in: iproute2 (Ubuntu) > Importance: Undecided => Wishlist > -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1508225 Title: tipc tool isn't built in iproute2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1508225/+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 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty
Having trouble with this still. I've installed the packages and made the changes to machine type and qemu as stated above. These are the errors I'm getting. 2015-10-23 19:25:57.491+: 7277: warning : qemuDomainObjEnterMonitorInternal:1274 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous 2015-10-23 19:25:57.583+: 7276: error : qemuMonitorIO:656 : internal error: End of file from monitor This is the command I used to migrate: virsh migrate --live --persistent --undefinesource --copy-storage-all --verbose test qemu+ssh://root@kvm15/system -- 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/1291321 Title: migration fails between 12.04 Precise and 14.04 Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1291321/+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 1509422] Re: package uses versioned shebangs
** Also affects: python-invoke (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-json-patch in Ubuntu. https://bugs.launchpad.net/bugs/1509422 Title: package uses versioned shebangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-bashate/+bug/1509422/+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 1509422] Re: package uses versioned shebangs
** Also affects: python-osprofiler (Ubuntu) Importance: Undecided Status: New ** Also affects: python-future (Ubuntu) Importance: Undecided Status: New ** Also affects: python-bashate (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-json-patch in Ubuntu. https://bugs.launchpad.net/bugs/1509422 Title: package uses versioned shebangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-bashate/+bug/1509422/+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 1509414] Re: lxc postinst script checks available interfaces, can choose
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 Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1509414 Title: lxc postinst script checks available interfaces, can choose To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1481295] Re: virt-manager after upgrade: Error polling connection 'qemu:///system': internal error: could not get interface XML description: File operation failed - Failed to read (null)
Putthing this in debian/patch/fix-virtmanager and adding fix-virtmanager to debian/patch/series solved this issue: diff --git a/src/dutil_linux.c b/src/dutil_linux.c index a3b0176..5d69d19 100644 --- a/src/dutil_linux.c +++ b/src/dutil_linux.c @@ -1041,7 +1041,14 @@ static void add_link_info(struct netcf *ncf, ERR_NOMEM(!path, ncf); state = read_file(path, &length); FREE(path); -ERR_THROW_STRERROR(!state, ncf, EFILE, "Failed to read %s", path); +if (!state) { +/* missing operstate is *not* an error. It could be due to an + * alias interface, which has not entry in /sys/class/net at + * all, for example. + */ +state = strdup(""); +ERR_NOMEM(!state, ncf); +} if ((nl = strchr(state, '\n'))) *nl = 0; prop = xmlSetProp(link_node, BAD_CAST "state", BAD_CAST state); -- 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 'qemu:///system': internal error: could not get interface XML description: File operation failed - Failed to read (null) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcf/+bug/1481295/+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 1481295] Re: virt-manager after upgrade: Error polling connection 'qemu:///system': internal error: could not get interface XML description: File operation failed - Failed to read (null)
The root cause is netcf not handling network alias https://bugzilla.redhat.com/show_bug.cgi?id=1185850 https://rhn.redhat.com/errata/RHBA-2015-0363.html Patch located in this post: https://lists.fedorahosted.org/pipermail/netcf-devel/2015-January/000924.html ** Also affects: netcf (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Red Hat Bugzilla #1185850 https://bugzilla.redhat.com/show_bug.cgi?id=1185850 -- 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 'qemu:///system': internal error: could not get interface XML description: File operation failed - Failed to read (null) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcf/+bug/1481295/+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 1509457] [NEW] SMBD User authentication doesn't work after dist upgrade to 15.10
Public bug reported: After upgrading to 15.10 my samba share stopped working. Guest shares work, but user authentication does not. After browsing to the share the user and password prompt is displayed but fails even with the correct credentials. I tried purging the samba packages and rewriting the configuration from a clean copy of /etc/samba/smb.conf The user is present in smbpasswd. The share configuration is of the form: [myshare] guest ok = no path = /home/username/myshare browseable = yes read only = no valid users = username user = username As a workaround I created a linux container for ubuntu 15.04, installed samba, used the same configuration, created the user, mounted the users home directory using --bind, and forwarded ports 139, and 445 and was able to get it to work. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: samba 2:4.1.17+dfsg-4ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 BothFailedConnect: Yes Date: Fri Oct 23 12:35:26 2015 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SambaServerRegression: Yes SmbConfIncluded: No SourcePackage: samba UpgradeStatus: Upgraded to wily on 2015-10-22 (1 days ago) upstart.smbd.override: manual ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1509457 Title: SMBD User authentication doesn't work after dist upgrade to 15.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1509457/+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 1509414] Re: lxc postinst script checks available interfaces, can choose
Not sure I like this approach. An init script should never change a system config, so this is a packaging policy violation... To be fair, anything we come up with which picks a random/unused subnet will still break users who may have this subnet in use behind a router, so that's not really an option either. For wily, I'd say we simply turn lxc-net off completely. That will add an extra step for any user who wants to use LXD, but it will also guarantee we don't regress anyone in the process. Doing so would require the CPC team to update /etc/default/lxc-net, setting USE_LXC_BRIDGE to false. -- 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/1509414 Title: lxc postinst script checks available interfaces, can choose To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509414] Re: lxc postinst script checks available interfaces, can choose
** Description changed: [Problem] The released wily image preinstalls lxc, which breaks the assumption that lxc's preinst packaging script makes: It inspects the network to try to pick a 10.0.N.0 network that isn't being used, with N starting at 3, so this appears to have picked 10.0.3.0 when it was installed on whatever system was generating the image. This conflicts with the network that eth0 gets attached to when the image is brought up in a container, because it gets attached to the host's lxcbr0, which is using 10.0.3.x. - This affects LXC, and should affect LXD but doesn't currently. (see #2) + This affects LXC, and should affect LXD but doesn't currently, as the metadata used for lxd images is still pointing to a beta2 release. The easiest way to reproduce this is to use the ubuntu-cloud lxc template on a wily host: [Test Case] sudo lxc-create -t ubuntu-cloud -n wily sudo lxc-start -n wily sudo lxc-attach -n wily # inside container, test connectivity, eg: apt-get update [Regression Potentional] Currently none as networking didn't work initially. -- 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/1509414 Title: lxc postinst script checks available interfaces, can choose To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509414] Re: lxc postinst script checks available interfaces, can choose
** Description changed: - The released wily image preinstalls lxc, which breaks the assumption - that lxc's preinst packaging script makes: + [Problem] + The released wily image preinstalls lxc, which breaks the assumption that lxc's preinst packaging script makes: It inspects the network to try to pick a 10.0.N.0 network that isn't being used, with N starting at 3, so this appears to have picked 10.0.3.0 when it was installed on whatever system was generating the image. This conflicts with the network that eth0 gets attached to when the image is brought up in a container, because it gets attached to the host's lxcbr0, which is using 10.0.3.x. This affects LXC, and should affect LXD but doesn't currently. (see #2) The easiest way to reproduce this is to use the ubuntu-cloud lxc template on a wily host: + [Test Case] + sudo lxc-create -t ubuntu-cloud -n wily sudo lxc-start -n wily sudo lxc-attach -n wily # inside container, test connectivity, eg: apt-get update + + [Regression Potentional] + Currently none as networking didn't work initially. -- 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/1509414 Title: lxc postinst script checks available interfaces, can choose To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509414] Re: lxc postinst script checks available interfaces, can choose
Debdiff which works for me. I tested this by creating a cloud container, temporarily setting USE_LXC_BRIDGE=false, rebooting, building the package, setting USE_LXC_BRIDGE=true (leaving 10.0.3 as the lxcbr0 subnet), rebooting. lxcbr0 comes up with 10.0.4.1 as expected. A nested trusty container works fine. The package is targeted at wily, should be at xenial presumably. That should be the only needed update. ** Patch added: "lxcnet.debdiff" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+attachment/4503325/+files/lxcnet.debdiff -- 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/1509414 Title: lxc postinst script checks available interfaces, can choose To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509422] [NEW] package uses versioned shebangs
Public bug reported: as seen in https://launchpadlibrarian.net/222329745/buildlog_ubuntu-xenial-amd64.python-json-patch_1.3-5build1_BUILDING.txt.gz the package builds with 3.5 as the default, but still depends on 3.4, because of the homegrown install step. please use vanilla pybuild to avoid these versioned dependencies. seen on more packages. like python-rtslib-fb ** Affects: python-json-patch (Ubuntu) Importance: Undecided Status: New ** Affects: python-rtslib-fb (Ubuntu) Importance: Undecided Status: New ** Also affects: python-rtslib-fb (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-json-patch in Ubuntu. https://bugs.launchpad.net/bugs/1509422 Title: package uses versioned shebangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-json-patch/+bug/1509422/+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 1509414] Re: lxc postinst script checks available interfaces, can choose
** Changed in: lxc (Ubuntu) Importance: Undecided => Critical -- 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/1509414 Title: lxc postinst script checks available interfaces, can choose To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1508565] Re: maas uses 3.13 (hwe-t) kernel which does not work on non-virtual IBM power
> Can a MaaS customer still get the hwe-t kernel through manual steps if desired? they could apt-get install it after the fact (same as for option 'b'). > What are consequences to support on hwe-u? Are they know forced up to 16.04 sooner (since hwe-u does not have lifetime of hwe-t)? Well, no. see [1], specifically the picture at [2]. An installed system would get updates on the installed 'linux-generic-lts-' kernel until August of 2016 (the release of 14.04.5). At that point, they no longer get kernel updates, but get a message that says "You should upgrade to linux-generic-lts-xeniel'.Also note, that your question really should say hwe-v. My testing showed that hwe-v would be selected if available, and we should make it availble in the released stream (as it is offiically released). > Or anyone wanting to recreate specific certification needs to know what the point in time kernel was... Cert has this general issue. We have no 'snapshot.ubuntu.com' (see http://snapshot.debian.org/ for reference), so there is actually no way to reproduce a point in time of ubuntu other than GA (because you can jsut disable -security and -updates to get GA only). Ie, as soon as you hit archive, you can only get updates. [1] https://wiki.ubuntu.com/Kernel/LTSEnablementStack [2] https://wiki.ubuntu.com/Kernel/LTSEnablementStack#Kernel.2BAC8-Support.A14.04.x_Ubuntu_Kernel_Support -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1508565 Title: maas uses 3.13 (hwe-t) kernel which does not work on non-virtual IBM power To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1508565/+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 1509414] Re: lxc postinst script checks available interfaces, can choose
Does not affect LXD only because the LXD metadata for simple-streams is out of date. We are going to hold off updating it until this bug is fixed and sru'ed. -- 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/1509414 Title: lxc postinst script checks available interfaces, can choose To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509414] Re: lxc postinst script checks available interfaces, can choose
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lxc (Ubuntu) Status: New => Confirmed -- 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/1509414 Title: lxc postinst script checks available interfaces, can choose To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509414] Re: lxc postinst script checks available interfaces, can choose
** Tags added: cloud-installer -- 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/1509414 Title: lxc postinst script checks available interfaces, can choose To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509414] [NEW] lxc postinst script checks available interfaces, can choose
Public bug reported: The released wily image preinstalls lxc, which breaks the assumption that lxc's preinst packaging script makes: It inspects the network to try to pick a 10.0.N.0 network that isn't being used, with N starting at 3, so this appears to have picked 10.0.3.0 when it was installed on whatever system was generating the image. This conflicts with the network that eth0 gets attached to when the image is brought up in a container, because it gets attached to the host's lxcbr0, which is using 10.0.3.x. This affects LXC, and should affect LXD but doesn't currently. (see #2) The easiest way to reproduce this is to use the ubuntu-cloud lxc template on a wily host: sudo lxc-create -t ubuntu-cloud -n wily sudo lxc-start -n wily sudo lxc-attach -n wily # inside container, test connectivity, eg: apt-get update ** Affects: lxc (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: cloud-installer -- 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/1509414 Title: lxc postinst script checks available interfaces, can choose To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509404] [NEW] snappy build does not allow abstract sockets with 'listen-stream'
Public bug reported: systemd socket activation (http://www.freedesktop.org/software/systemd/man/systemd.socket.html) was added to the service yaml some time ago. ListenStream= in the systemd unit supports both file-based sockets (start with '/') and abstract sockets (start with '@'). However, snappy build doesn't recognize '@' as a valid character. $ cat ./meta/package.yaml name: foo version: 1.3 vendor: Some One icon: meta/hello.png services: - name: bar start: bin/bar description: bar service socket: true listen-stream: '@foo_bar' $ snappy build . services description field 'ListenStream' contains illegal '@foo_bar' (legal: '^[A-Za-z0-9/. _#:-]*$') Couple of things here: a) the error message should say 'listen-stream', not 'ListenStream' because we want to reference the packaging yaml declaration, not the underlying systemd implementation b) '@' should be allowed in this regex. Based on the existing error regex, I suggest it be changed to: '^[/@][A-Za-z0-9/. _#:-]+$' ** Affects: snappy (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to snappy in Ubuntu. https://bugs.launchpad.net/bugs/1509404 Title: snappy build does not allow abstract sockets with 'listen-stream' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snappy/+bug/1509404/+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 1509396] [NEW] Missing dependency on python-setuptools
Public bug reported: Flake8 uses setuptools in flake8/main.py: import setuptools but the binary packages do not depend on it. It used to work in many cases because the pep8 package that python-flake8 depends on was depending on setuptools, but not anymore since version 1.6.2-0.1ubuntu1 uploaded to xenial just now. See diff and corresponding bug report: http://launchpadlibrarian.net/222126620/pep8_1.6.2-0.1_1.6.2-0.1ubuntu1.diff.gz https://bugs.launchpad.net/ubuntu/+source/pep8/+bug/1414491 ** Affects: python-flake8 (Ubuntu) Importance: High Assignee: Matthias Klose (doko) Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-flake8 in Ubuntu. https://bugs.launchpad.net/bugs/1509396 Title: Missing dependency on python-setuptools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-flake8/+bug/1509396/+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 1509147] Re: [SRU] MAAS 1.8.3
** Description changed: = Changelog = - 1.8.3 = See https://launchpad.net/maas/+milestone/1.8.3 for full details. Bug Fix Update -- - #1495064Declare dependency on metadataserver migration 0015 by maasserver - migration 0121 to allow upgrades from 1.5.4 to 1.8 to work. - - #1484696Fix the issue where the included ':', apache2 wont forward the - connection (LP: #1484696) + #1495064Declare dependency on metadataserver migration 0015 by + maasserver migration 0121 to allow upgrades from 1.5.4 to 1.8 to work. + + #1484696Fix the issue where the included ':', apache2 wont forward + the connection (LP: #1484696) #1489160WebUI - Fixes autocomplete styling for tagging #1491898Add HPDSA hardware drivers to the drivers config #1491822Always invoke the init system using the C.UTF-8 locale. #1471946Restart maas-clusterd in the event of startup failure due to - missing /var/lib/maas/secret + missing /var/lib/maas/secret #1483273Use Cluster's name instead of DNS name for the WebUi. - #1504971Internal Server Error when trying to configure a cluster interface - in wily. - + #1504971Internal Server Error when trying to configure a cluster + interface in wily. 1.8.2 = See https://launchpad.net/maas/+milestone/1.8.2 for full details. Bug Fix Update -- - #1484696Regenerate the connection URL on websocket client reconnect, to fix - CSRF after upgrade to 1.8.1. - - #1445942Validate the osystem and distro_series when using the deploy action, - which fixes win2012r2 deployment issues. - - #1481940Fix failure in MAAS startup messages by not generating dhcpd config - files when they are not in use. + #1484696Regenerate the connection URL on websocket client reconnect, + to fix CSRF after upgrade to 1.8.1. + + #1445942Validate the osystem and distro_series when using the deploy + action, which fixes win2012r2 deployment issues. + + #1481940Fix failure in MAAS startup messages by not generating dhcpd + config files when they are not in use. #1459865Fix enlistment to always use the correct kernel parameters. - 1.8.1 = See https://launchpad.net/maas/+milestone/1.8.1 for full details. Bug Fix Update -- #1481118Add --username to maas-region-admin apikey command docs. - #1472707Add ListBootImagesV2 RPC command. Fallback to using ListBootImages RPC - when the ListBootImagesV2 is not handled on the cluster. + #1472707Add ListBootImagesV2 RPC command. Fallback to using + ListBootImages RPC when the ListBootImagesV2 is not handled on the + cluster. #1470591Fix setting the default_distro_series over the API. #1413388Fix upgrade issue where it would remove custom DNS config, potentially breaking DNS #1317705Commissioning x86_64 node never completes, sitting at grub prompt, pserv py tbs #1389007Power monitor service hits amp.TooLong errors with > ~600 nodes to a cluster #1436279Websocket server accessed over port 5240 #1469305If hostname not set, sudo warning make maas throw 500 #1470585Can't set a list of forwarders (BIND config) #1469846UCS chassis enlist Failed to probe and enlist UCS nodes: list index out of range #1470276Add cisco snic to 3rd party driver #1402042console= parameters need to be added before -- on kernel cmdline #1465722[UI] Machine details styling #1465737[UI] Actions design styles #1465740[UI] Replace close "X" with correct versions #1465742[UI] Table design styles #1470389[UI] Make table heading hover consistant with nodes/devices tabs #1470395[UI] adding between node name and save button inconsistent #1459710[UI] "Set zone" label oddly placed on node listing page - 1.8.0 = Important announcements --- **Region Controller now running on twisted.** - The MAAS Region Controller is now running as a twisted daemon. It is - no longer dependent on Apache in order to run. The MAAS Region - controller is now controlled by ``maas-regiond`` upstart job or systemd - unit. The ``maas-regiond`` daemon is available in port ``5240``. + The MAAS Region Controller is now running as a twisted daemon. It is + no longer dependent on Apache in order to run. The MAAS Region + controller is now controlled by ``maas-regiond`` upstart job or systemd + unit. The ``maas-regiond`` daemon is available in port ``5240``. **Firewall ports for Region and Cluster controller communication** - The communication between Region and Cluster controller is now limited - to use the ports between ``5250`` and ``5259``. For all of those users who - are using a remote cluster (not runni
[Bug 1411176] Re: Please remove python-oauth2 package from Ubuntu repo
Reviews on screenlets indicate this is still useful to someone in 2014. (3 Stars), closing that task as it's not blocking anything. ** Changed in: indiv-screenlets (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-oauth2 in Ubuntu. https://bugs.launchpad.net/bugs/1411176 Title: Please remove python-oauth2 package from Ubuntu repo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/django-oauth-plus/+bug/1411176/+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 1504781] Re: lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66: AppArmor denies /dev/ptmx mounting
Judging by jjohansen's comment #8, I guess the shipped common configuration files in precise's lxc should be updated to include the new rule. Precise's lxc is in universe, community supported. Can you provide a proposed, tested debdiff and ping me? I'll sponsor it when ready if needed. -- 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/1504781 Title: lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66: AppArmor denies /dev/ptmx mounting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504781/+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 1214806] Re: pinger crashed with SIGSEGV in __tzfile_compute()
I think the pinger is an optional component in Squid. As a workaround it might help to set "pinger_enable off" in /etc/squid3/squid.conf. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1214806 Title: pinger crashed with SIGSEGV in __tzfile_compute() To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1214806/+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 1509356] [NEW] pep8 depends on python3-pep, not python3-pep8
Public bug reported: As seen in http://launchpadlibrarian.net/222126620/pep8_1.6.2-0.1_1.6.2-0.1ubuntu1.diff.gz pep8 starts depending on python3-pep while the package is python3-pep8 (or python-pep8). This prevents currently building packages that depend on pep8. ** Affects: pep8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pep8 in Ubuntu. https://bugs.launchpad.net/bugs/1509356 Title: pep8 depends on python3-pep, not python3-pep8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pep8/+bug/1509356/+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 1346740] Re: drac plugin in dovecot uses wrong plugin version string
Same issue like Guillaume. Please set importance to high. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/1346740 Title: drac plugin in dovecot uses wrong plugin version string To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1346740/+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 1346740] Re: drac plugin in dovecot uses wrong plugin version string
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dovecot (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/1346740 Title: drac plugin in dovecot uses wrong plugin version string To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1346740/+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 1346740] Re: drac plugin in dovecot uses wrong plugin version string
Same issue with Ubuntu 14.04 AMD64. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/1346740 Title: drac plugin in dovecot uses wrong plugin version string To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1346740/+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
Re: [Bug 1501217] Re: Removing squid-deb-proxy-client leaves a stale but active config file, breaking apt
Thank you for trying. It might be a reasonable feature request for apt to make it possible to call a shell or to provide arguments so that we can call a shell though, in order to resolve this bug. It would be a reasonably generic solution. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid-deb-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1501217 Title: Removing squid-deb-proxy-client leaves a stale but active config file, breaking apt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1501217/+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 1509083] Re: Backport Apache fix "Honor ProxyTimeout" (54973)
I can help you to identify the upstream patch in upstream VCS for now ;) The revision: http://svn.apache.org/viewvc?view=revision&revision=1524368 The path: http://svn.apache.org/viewvc/httpd/httpd/trunk/modules/proxy/mod_proxy_fcgi.c?r1=1524368&r2=1524367&pathrev=1524368&view=patch Regards, -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1509083 Title: Backport Apache fix "Honor ProxyTimeout" (54973) To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1509083/+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 1501217] Re: Removing squid-deb-proxy-client leaves a stale but active config file, breaking apt
Experiments show that Acquire::http::ProxyAutoDetect "/bin/sh -c 'true'"; produces this error: Failed to exec method /bin/sh -c 'true' so I'm afraid options 1 and 2 are out :( -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid-deb-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1501217 Title: Removing squid-deb-proxy-client leaves a stale but active config file, breaking apt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1501217/+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 1509094] Re: package mysql-common 5.6.25-0ubuntu1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück
Thank you for taking the time to report this bug and helping to make Ubuntu better. Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete. If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: mysql-5.6 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1509094 Title: package mysql-common 5.6.25-0ubuntu1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1509094/+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 1509083] Re: Backport Apache fix "Honor ProxyTimeout" (54973)
Hi Robin, Thank you for taking the time to report this bug and helping to make Ubuntu better. This request looks reasonable to me. I'll add it to the queue. To help process it faster, we will need: Identification of the upstream patch in upstream VCS (commit ID and preferably a link to the commit in a web view of the VCS). Manual verification by a developer that the patch is still applicable to the version in 14.04. A test case with step by step instructions on how to reproduce the issue on 14.04. The full procedure is documented at: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure Thanks ** Tags added: bitesize ** Also affects: apache2 (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: apache2 (Ubuntu Trusty) Status: New => Triaged ** Changed in: apache2 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1509083 Title: Backport Apache fix "Honor ProxyTimeout" (54973) To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1509083/+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 1509083] [NEW] Backport Apache fix "Honor ProxyTimeout" (54973)
You have been subscribed to a public bug by Robie Basak (racb): As suggested by Manfred Hampl, I now open a bug report from this question: I use Apache 2.4.7 with mod_proxy_fcgi which is affected of this bug: https://bz.apache.org/bugzilla/show_bug.cgi?id=54973 . Is it possible to backport this patch to 2.4.7 (fixed in 2.4.8, see link @ bottom page)? Would be nice to use timeouts higher than 30 seconds ;) My system is an up-to-date Ubuntu Server 14.04.3 LTS with Apache 2.4.7-1ubuntu4.8 Thanks in advance! ** Affects: apache2 Importance: Critical Status: Fix Released ** Affects: apache2 (Ubuntu) Importance: Undecided Status: New ** Tags: bitesize -- Backport Apache fix "Honor ProxyTimeout" (54973) https://bugs.launchpad.net/bugs/1509083 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. -- 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 1504781] Re: lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66: AppArmor denies /dev/ptmx mounting
As Eugene said, there is a bug affecting precise with the latest 3.2 and 3.13 (supported LTS trusty kernel for precise) and the official LXC package. No backports or ppa used. The bug is marked as duplicate but no fix for 12.04 is released. -- 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/1504781 Title: lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66: AppArmor denies /dev/ptmx mounting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504781/+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