[Bug 911922] Re: libnss-ldap:i386 does not install
[Expired for libnss-ldap (Ubuntu Precise) because there has been no activity for 60 days.] ** Changed in: libnss-ldap (Ubuntu Precise) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libnss-ldap in Ubuntu. https://bugs.launchpad.net/bugs/911922 Title: libnss-ldap:i386 does not install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/911922/+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 625812] Re: Install needs to turn off Reverse Path Filtering
It's not a bug! most of linux servers are not routers and specially not with bgp that there there is a big options that a packet will go out using one interface but the answer will get through another interface\route. if you are operating a BGP router you should be aware of this issue in linux distros. what can be done is to add like "forwarding" option in zebra\vtysh an options to disable rp_filter using quagga interface. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to quagga in Ubuntu. https://bugs.launchpad.net/bugs/625812 Title: Install needs to turn off Reverse Path Filtering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/quagga/+bug/625812/+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 941874] Re: (fakeraid) root device not activated during boot
** Changed in: dmraid (Ubuntu) Milestone: None => ubuntu-12.04 ** Changed in: multipath-tools (Ubuntu) Milestone: None => ubuntu-12.04 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/941874 Title: (fakeraid) root device not activated during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+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 941874] Re: (fakeraid) root device not activated during boot
** Changed in: dmraid (Ubuntu) Importance: High => Critical ** Changed in: multipath-tools (Ubuntu) Importance: High => Critical -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/941874 Title: (fakeraid) root device not activated during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+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 945177] Re: not lintian clean
Did a bunch of house-cleaning on the nova packaging today, current list of offences has dropped considerably, but still needs some work: W: nova-compute: executable-not-elf-or-script usr/share/pyshared/nova/rootwrap/compute.py W: nova-compute: maintainer-script-needs-depends-on-adduser postinst W: nova-compute-xcp: empty-binary-package W: nova-network: executable-not-elf-or-script usr/share/pyshared/nova/rootwrap/network.py W: nova-ajax-console-proxy: transitional-package-should-be-oldlibs-extra net/extra W: nova-vncproxy: binary-without-manpage usr/bin/nova-xvpvncproxy W: nova-volume: executable-not-elf-or-script usr/share/pyshared/nova/rootwrap/volume.py -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/945177 Title: not lintian clean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/945177/+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 959352] Re: Ephemeral containers have "/rootfs" prefix in /proc/self/maps entries
Thank you for taking the time to file a bug report on this issue. However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request. We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not. You can update to the latest development kernel by simply running the following commands in a terminal window: sudo apt-get update sudo apt-get dist-upgrade If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released. If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging. Thank you for your help, we really do appreciate it. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: kernel-request-3.2.0-21.34 -- 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/959352 Title: Ephemeral containers have "/rootfs" prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 969604] Re: lxc-stop should be able to handle ephemeral containers more robustly
I agree. I was thinking as I wrote this that we would be awfully close to being able to get rid of the -- COMMAND stuff if this were implemented, for instance; and generally close to being able to make lxc-start-ephemeral behave very similarly to lxc-start in terms of interaction patterns. Unfortunately I won't be at UDS. -- 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/969604 Title: lxc-stop should be able to handle ephemeral containers more robustly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/969604/+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 802117] Re: juju ssh command should use a different known_hosts file
** Summary changed: - ensemble ssh command should use a different known_hosts file + juju ssh command should use a different known_hosts file ** Description changed: With lots of instances, one occasionally finds themselves using the same twice. - Ensemble ssh should use a unique known_hosts file per environment, so as - not to pollute the user's main known_hosts file. + juju ssh should use a unique known_hosts file per environment, so as not + to pollute the user's main known_hosts file. ** Also affects: juju (Ubuntu) Importance: Undecided Status: New ** Summary changed: - juju ssh command should use a different known_hosts file + juju ssh/scp commands cause spurious key errors, should use a different known_hosts file ** Changed in: juju (Ubuntu) Status: New => Triaged ** Changed in: juju (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/802117 Title: juju ssh/scp commands cause spurious key errors, should use a different known_hosts file To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/802117/+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 962373] Re: unhelpful error message when .ssh/known_hosts doesn't match
*** This bug is a duplicate of bug 802117 *** https://bugs.launchpad.net/bugs/802117 Jamie, I don't think we should hide the fact that we're using OpenSSH or deviate from OpenSSH's error messages on this one. In fact, I think juju should do more to populate and manage the known_hosts file, since juju is responsible for those systems' provisioning. This is covered in bug #802117, which suggests that at the very minimum, each environment should get its own known_hosts file. I think that would solve the problem of spurious SSH warnings that you saw. Given that, I am marking this as a duplicate of that bug. ** This bug has been marked a duplicate of bug 802117 juju ssh command should use a different known_hosts file -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/962373 Title: unhelpful error message when .ssh/known_hosts doesn't match To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/962373/+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 959426] Re: nova + glance services die if started before db is reachable
Reviewed: https://review.openstack.org/5939 Committed: http://github.com/openstack/nova/commit/a4dd6b6f06d222f49bd0d2582dfe0f2925a1638f Submitter: Jenkins Branch:master commit a4dd6b6f06d222f49bd0d2582dfe0f2925a1638f Author: Adam Gandelman Date: Wed Mar 28 18:52:41 2012 -0700 Ensure a functional database connection Allow retrying database connection in get_engine() at an interval. Resolves the issue of nova components erroring at startup if a database connection is unavailable, particularly at boot. Borrowed from a similar commit to glance, (https://review.openstack.org/#change,5552). Fixes Bug #959426 for nova. Update: * Properly return an engine (fixes tests) * Setting sql_max_retries to -1 will retry infinitely * Bumped options count in nova.conf.sample * i18n log warning * Add note to flag help about -1 == infinite * Pep8 fix Change-Id: Id34eda9e0bad6b477a74e9a7d3575e513e6291d5 ** Changed in: nova Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/959426 Title: nova + glance services die if started before db is reachable To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/959426/+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 957682] Re: juju crashed with IOError in write_sample(): [Errno 13] Permission denied: '/home/username/.juju/environments.yaml'
** Branch linked: lp:ubuntu/juju -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/957682 Title: juju crashed with IOError in write_sample(): [Errno 13] Permission denied: '/home/username/.juju/environments.yaml' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/957682/+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 953258] Re: juju executing hooks with umask of 0077
This bug was fixed in the package juju - 0.5+bzr504-0ubuntu1 --- juju (0.5+bzr504-0ubuntu1) precise; urgency=low * New upstream snapshot (LP: #962507 LP: #953258 LP: #965507). * d/control: Depend and Build-Depend on python-oauth for MaaS. * d/control: Drop dummy ensemble package and make breaks/replaces broader to force removal of any ensemble package. (LP: #954492) * d/control: Move lxc, libvirt-bin, and zookeeper to Suggests to reduce the amount of packages installed on every node unecessarily and also avoid conflicting when deploying into a libvirt-bin default network VM (LP: #962389) * d/rules: skip test suite when nocheck is set. * d/rules: remove redundant dh_clean call * d/juju.install: remove usr, with only one binary package this is not necessary anymore and causes dh_install to fail because no files are installed to debian/tmp anymore. * d/rules,d/control,d/manpages,d/juju.manpages: Generate basic manpage from online help. (LP: #966611) * d/patches/no-write-sample-on-help.patch: Added so --help can be safely run without a writable home dir on buildds. (LP: #957682) -- Clint ByrumFri, 30 Mar 2012 15:28:16 -0700 ** Changed in: juju (Ubuntu Precise) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/953258 Title: juju executing hooks with umask of 0077 To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/953258/+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 954492] Re: dummy ensemble package should be dropped
This bug was fixed in the package juju - 0.5+bzr504-0ubuntu1 --- juju (0.5+bzr504-0ubuntu1) precise; urgency=low * New upstream snapshot (LP: #962507 LP: #953258 LP: #965507). * d/control: Depend and Build-Depend on python-oauth for MaaS. * d/control: Drop dummy ensemble package and make breaks/replaces broader to force removal of any ensemble package. (LP: #954492) * d/control: Move lxc, libvirt-bin, and zookeeper to Suggests to reduce the amount of packages installed on every node unecessarily and also avoid conflicting when deploying into a libvirt-bin default network VM (LP: #962389) * d/rules: skip test suite when nocheck is set. * d/rules: remove redundant dh_clean call * d/juju.install: remove usr, with only one binary package this is not necessary anymore and causes dh_install to fail because no files are installed to debian/tmp anymore. * d/rules,d/control,d/manpages,d/juju.manpages: Generate basic manpage from online help. (LP: #966611) * d/patches/no-write-sample-on-help.patch: Added so --help can be safely run without a writable home dir on buildds. (LP: #957682) -- Clint ByrumFri, 30 Mar 2012 15:28:16 -0700 ** Changed in: juju (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/954492 Title: dummy ensemble package should be dropped To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/954492/+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 957682] Re: juju crashed with IOError in write_sample(): [Errno 13] Permission denied: '/home/username/.juju/environments.yaml'
This bug was fixed in the package juju - 0.5+bzr504-0ubuntu1 --- juju (0.5+bzr504-0ubuntu1) precise; urgency=low * New upstream snapshot (LP: #962507 LP: #953258 LP: #965507). * d/control: Depend and Build-Depend on python-oauth for MaaS. * d/control: Drop dummy ensemble package and make breaks/replaces broader to force removal of any ensemble package. (LP: #954492) * d/control: Move lxc, libvirt-bin, and zookeeper to Suggests to reduce the amount of packages installed on every node unecessarily and also avoid conflicting when deploying into a libvirt-bin default network VM (LP: #962389) * d/rules: skip test suite when nocheck is set. * d/rules: remove redundant dh_clean call * d/juju.install: remove usr, with only one binary package this is not necessary anymore and causes dh_install to fail because no files are installed to debian/tmp anymore. * d/rules,d/control,d/manpages,d/juju.manpages: Generate basic manpage from online help. (LP: #966611) * d/patches/no-write-sample-on-help.patch: Added so --help can be safely run without a writable home dir on buildds. (LP: #957682) -- Clint ByrumFri, 30 Mar 2012 15:28:16 -0700 ** Changed in: juju (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/957682 Title: juju crashed with IOError in write_sample(): [Errno 13] Permission denied: '/home/username/.juju/environments.yaml' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/957682/+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 962389] Re: juju Recommends on lxc installs libvirt-bin which causes problems when testing in virtualized environments
This bug was fixed in the package juju - 0.5+bzr504-0ubuntu1 --- juju (0.5+bzr504-0ubuntu1) precise; urgency=low * New upstream snapshot (LP: #962507 LP: #953258 LP: #965507). * d/control: Depend and Build-Depend on python-oauth for MaaS. * d/control: Drop dummy ensemble package and make breaks/replaces broader to force removal of any ensemble package. (LP: #954492) * d/control: Move lxc, libvirt-bin, and zookeeper to Suggests to reduce the amount of packages installed on every node unecessarily and also avoid conflicting when deploying into a libvirt-bin default network VM (LP: #962389) * d/rules: skip test suite when nocheck is set. * d/rules: remove redundant dh_clean call * d/juju.install: remove usr, with only one binary package this is not necessary anymore and causes dh_install to fail because no files are installed to debian/tmp anymore. * d/rules,d/control,d/manpages,d/juju.manpages: Generate basic manpage from online help. (LP: #966611) * d/patches/no-write-sample-on-help.patch: Added so --help can be safely run without a writable home dir on buildds. (LP: #957682) -- Clint ByrumFri, 30 Mar 2012 15:28:16 -0700 ** Changed in: juju (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/962389 Title: juju Recommends on lxc installs libvirt-bin which causes problems when testing in virtualized environments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/962389/+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 962507] Re: [FFE] Latest juju snapshot enables maas provider
This bug was fixed in the package juju - 0.5+bzr504-0ubuntu1 --- juju (0.5+bzr504-0ubuntu1) precise; urgency=low * New upstream snapshot (LP: #962507 LP: #953258 LP: #965507). * d/control: Depend and Build-Depend on python-oauth for MaaS. * d/control: Drop dummy ensemble package and make breaks/replaces broader to force removal of any ensemble package. (LP: #954492) * d/control: Move lxc, libvirt-bin, and zookeeper to Suggests to reduce the amount of packages installed on every node unecessarily and also avoid conflicting when deploying into a libvirt-bin default network VM (LP: #962389) * d/rules: skip test suite when nocheck is set. * d/rules: remove redundant dh_clean call * d/juju.install: remove usr, with only one binary package this is not necessary anymore and causes dh_install to fail because no files are installed to debian/tmp anymore. * d/rules,d/control,d/manpages,d/juju.manpages: Generate basic manpage from online help. (LP: #966611) * d/patches/no-write-sample-on-help.patch: Added so --help can be safely run without a writable home dir on buildds. (LP: #957682) -- Clint ByrumFri, 30 Mar 2012 15:28:16 -0700 ** Changed in: juju (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/962507 Title: [FFE] Latest juju snapshot enables maas provider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/962507/+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 965507] Re: Juju uses http to contact uec-images.ubuntu.com
This bug was fixed in the package juju - 0.5+bzr504-0ubuntu1 --- juju (0.5+bzr504-0ubuntu1) precise; urgency=low * New upstream snapshot (LP: #962507 LP: #953258 LP: #965507). * d/control: Depend and Build-Depend on python-oauth for MaaS. * d/control: Drop dummy ensemble package and make breaks/replaces broader to force removal of any ensemble package. (LP: #954492) * d/control: Move lxc, libvirt-bin, and zookeeper to Suggests to reduce the amount of packages installed on every node unecessarily and also avoid conflicting when deploying into a libvirt-bin default network VM (LP: #962389) * d/rules: skip test suite when nocheck is set. * d/rules: remove redundant dh_clean call * d/juju.install: remove usr, with only one binary package this is not necessary anymore and causes dh_install to fail because no files are installed to debian/tmp anymore. * d/rules,d/control,d/manpages,d/juju.manpages: Generate basic manpage from online help. (LP: #966611) * d/patches/no-write-sample-on-help.patch: Added so --help can be safely run without a writable home dir on buildds. (LP: #957682) -- Clint ByrumFri, 30 Mar 2012 15:28:16 -0700 ** Changed in: juju (Ubuntu Precise) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/965507 Title: Juju uses http to contact uec-images.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/965507/+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 966611] Re: add man pages for juju commands
This bug was fixed in the package juju - 0.5+bzr504-0ubuntu1 --- juju (0.5+bzr504-0ubuntu1) precise; urgency=low * New upstream snapshot (LP: #962507 LP: #953258 LP: #965507). * d/control: Depend and Build-Depend on python-oauth for MaaS. * d/control: Drop dummy ensemble package and make breaks/replaces broader to force removal of any ensemble package. (LP: #954492) * d/control: Move lxc, libvirt-bin, and zookeeper to Suggests to reduce the amount of packages installed on every node unecessarily and also avoid conflicting when deploying into a libvirt-bin default network VM (LP: #962389) * d/rules: skip test suite when nocheck is set. * d/rules: remove redundant dh_clean call * d/juju.install: remove usr, with only one binary package this is not necessary anymore and causes dh_install to fail because no files are installed to debian/tmp anymore. * d/rules,d/control,d/manpages,d/juju.manpages: Generate basic manpage from online help. (LP: #966611) * d/patches/no-write-sample-on-help.patch: Added so --help can be safely run without a writable home dir on buildds. (LP: #957682) -- Clint ByrumFri, 30 Mar 2012 15:28:16 -0700 ** Changed in: juju (Ubuntu Precise) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/966611 Title: add man pages for juju commands To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/966611/+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 969604] Re: lxc-stop should be able to handle ephemeral containers more robustly
Thanks, Gary. To be honest, I think we should re-visit the goals of lxc-start- ephemeral at UDS-Q, and rewrite it to be more robust and focused. (Then we coudl also send the result upstream) ** Changed in: lxc (Ubuntu) Importance: Undecided => Low ** 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/969604 Title: lxc-stop should be able to handle ephemeral containers more robustly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/969604/+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 969604] [NEW] lxc-stop should be able to handle ephemeral containers more robustly
Public bug reported: It is possible to have an ephemeral container remaining after lxc-start- ephemeral has been killed--trivially by calling kill -9 on lxc-start- ephemeral. At that point, the script does not get a chance to clean up after itself, and the system is left with a running ephemeral container as well as several mounts. lxc-stop can stop the container, but after an ephemeral container is stopped, it ought to be destroyed, and it is not. Moreover, if you then try to use lxc-destroy, it will fail, because the ephemeral container's directory is mounted, with another directory mounted inside (ephemeralbind). Moreover again, if you succeed in umounting those directories, and then destroying the container, there is still a tmpfs "/tmp/lxc-lp-XXX" directory (I suspect that "lp" segment of the name is no longer appropriate, btw) hidden away consuming undefined amounts amount of memory that would ideally have been removed for the user. We have a script to handle this possibility in an automated way. Beyond handling the above, it does one more thing that lxc-stop can't do now: it finds all of the ephemeral containers via a glob, to allow the automated script to not have to know what temporary name the ephemeral container has. An equivalent would be "lxc-stop -n lptests-tmp-*". It would be nice if lxc-stop could handle properly destroying ephemeral containers when they are stopped. (Perhaps this could even be a step along the way to the non-COMMAND version of lxc-start-ephemeral ending simply with either lxc-start -n $NAME or lxc-start -d -n $NAME.) It would be even more nice if lxc-stop could handle globs, so we could do away with our script. The least obvious aspect of the implementation I see is how to know what /tmp/lxc-lp-* directory to remove. The best I can come up with is parsing the output of "mount" to find the tmp directory used as the "upperdir" for the primary overlayfs. This would be a bit more lines of code if you wanted to support aufs, but still doable. If it's not already clear, I personally consider this a low priority nice-to-have. Thank you ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/969604 Title: lxc-stop should be able to handle ephemeral containers more robustly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/969604/+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 859814] Re: Locale issues with beta-1/2 cloud-images
Added "language-pack-en" to all Precise builds. -- 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/859814 Title: Locale issues with beta-1/2 cloud-images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/859814/+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 969228] Re: Unable to load another apparmor profile from /etc/apparmor.d/lxc/
This bug was fixed in the package lxc - 0.7.5-3ubuntu48 --- lxc (0.7.5-3ubuntu48) precise; urgency=low * debian/lxc-default.apparmor: explicitly silence warnings about attempting to mount debugfs to /var/lib/ureadahead/debugfs/. * 0066-confile-typo: fix typo * debian/lxc.apparmor: allow transition to unconfined * 0067-templates-lxc-profile: leave a comment in container configs we create to show how to run it unconfined * debian/lxc-containers.apparmor: move #include from debian/lxc-default.apparmor here to prevent policy loading errors when more container profiles are defined (LP: #969228) * debian/lxc-default.apparmor: remove obsolete FIXME comment -- Serge HallynFri, 30 Mar 2012 15:35:07 -0500 ** Changed in: lxc (Ubuntu) Status: Confirmed => Fix 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/969228 Title: Unable to load another apparmor profile from /etc/apparmor.d/lxc/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/969228/+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 966115] Re: nova-api{,-os-compute,-ec2,-os-volume} relationship
** Changed in: nova (Ubuntu)
Importance: Undecided => High
** Changed in: nova (Ubuntu)
Status: New => In Progress
** Changed in: nova (Ubuntu)
Assignee: (unassigned) => Adam Gandelman (gandelman-a)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/966115
Title:
nova-api{,-os-compute,-ec2,-os-volume} relationship
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/966115/+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 968753] Re: ssh crashed with SIGSEGV
Actually I lied: that host is running CentOS-3 and it has the RSA PAM modules. Not sure which is the issue. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/968753 Title: ssh crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/968753/+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 969452] Re: SSH crashes after authorization
** Package changed: ubuntu => openssh (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/969452 Title: SSH crashes after authorization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/969452/+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 969452] [NEW] SSH crashes after authorization
You have been subscribed to a public bug: Hello!. After upgrading my system to ubuntu 12.04 beta version I've noticed that I cannot connect using ssh to any of my servers. e.g. #ssh -p55533 u...@host.com u...@host.com's password: Segmentation fault (core dumped) The issue arises both on the upgraded system and newly installed ubuntu 12.04 (I've installed it on another nootebook). So, it is defenitely smth. is not OK with ssh after upgrading. Information about my systems: 1) lsb_release -rd Description:Ubuntu precise (development branch) Release:12.04 2) apt-cache policy ssh ssh: Installed: 1:5.9p1-4ubuntu1 Candidate: 1:5.9p1-4ubuntu1 3) expected to login to my server via ssh 4) see above. Please let me know if I should provide you with any additional information. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ssh 1:5.9p1-4ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic i686 ApportVersion: 1.95-0ubuntu1 Architecture: i386 Date: Fri Mar 30 22:02:22 2012 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) PackageArchitecture: all ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openssh UpgradeStatus: Upgraded to precise on 2012-03-30 (0 days ago) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- SSH crashes after authorization https://bugs.launchpad.net/bugs/969452 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. -- 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
[Blueprint servercloud-q-eucalyptus] Eucalyptus updates in 12.10
Blueprint changed by Brian Thomason: Whiteboard set to: This session will begin as a brief presentation of the newly released Eucalyptus 3.0 and its new feature set which will soon be released as an Open Source offering in the Canonical Partner Repository. We will also discuss the idea of re-entering Universe for 12.10 onward. Following the brief intro, we will have a QA session where interested attendees can have their questions about 3.0/3.1 answered by the Eucalyptus engineering team. We will close with a roundtable discussion where attendees can express their ideas on future features with a focus on what can be done to improve community involvement in the project. -- Eucalyptus updates in 12.10 https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-eucalyptus -- 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 966611] Re: add man pages for juju commands
** Changed in: juju (Ubuntu Precise) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/966611 Title: add man pages for juju commands To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/966611/+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 966611] Re: add man pages for juju commands
** Branch linked: lp:ubuntu/juju -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/966611 Title: add man pages for juju commands To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/966611/+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
[Blueprint servercloud-q-eucalyptus] Eucalyptus updates in 12.10
Blueprint changed by Brian Thomason: Work items set to: Work items: [gholms] Gather feedback on euca2ools: TODO [agrimm] Gather feedback on ways to improve community involvement and contributions: TODO -- Eucalyptus updates in 12.10 https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-eucalyptus -- 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 959426] Re: nova + glance services die if started before db is reachable
** Changed in: nova Assignee: Vish Ishaya (vishvananda) => Adam Gandelman (gandelman-a) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/959426 Title: nova + glance services die if started before db is reachable To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/959426/+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 859814] Re: Locale issues with beta-1/2 cloud-images
** Description changed: Default locale of image appears to be en_US.UTF-8 - however when I logon from a en_GB.UTF-8 client via SSH I get the following errors - springs up in a few places while doing things on the server. This was from a local openstack test instance; however I get the same error in ec2 instances with the latest daily snapshot. ubuntu@server-3:~$ locale locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory LANG=en_US.UTF-8 LANGUAGE= LC_CTYPE=en_GB.UTF-8 LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE=en_GB.UTF-8 LC_MONETARY="en_US.UTF-8" LC_MESSAGES=en_GB.UTF-8 LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= Related Bugs: - * Bug 920601: cloud-images don't accept LANG settings + * Bug 920601: cloud-images don't accept LANG settings + * Bug 969462: postgresql-9.1 fails to start after install if invalid locale is set ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: cloud-init 0.6.1-0ubuntu15 ProcVersionSignature: User Name 3.0.0-9.15-virtual 3.0.3 Uname: Linux 3.0.0-9-virtual x86_64 Architecture: amd64 Date: Mon Sep 26 17:09:24 2011 Ec2AMI: ami-0002 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: aki-0001 Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: LC_CTYPE=en_GB.UTF-8 LC_COLLATE=en_GB.UTF-8 LANG=en_US.UTF-8 LC_MESSAGES=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: cloud-init 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/859814 Title: Locale issues with beta-1/2 cloud-images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/859814/+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 859814] Re: Locale issues with beta-1/2 cloud-images
Some more data here, the following results in postgresql not started on installation: $ LC_ALL=en_GB.UTF-8 ssh ubuntu@$HOSTNAME $ sudo apt-get install postgresql-9.1 ... Adding user postgres to group ssl-cert Building PostgreSQL dictionaries from installed myspell/hunspell packages... Setting up postgresql-9.1 (9.1.3-2) ... Error: The locale requested by the environment is invalid. Error: could not create default cluster. Please create it manually with pg_createcluster 9.1 main --start or a similar command (see 'man pg_createcluster'). If you run 'apt-get install language-pack-en' prior to running the above, it will work. It will still fail, though if you do: $ LC_ALL=fr_FR.UTF-8 ssh $ sudo apt-get install postgresql-9.1 (which would be fixed by 'apt-get install language-pack-fr'). -- 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/859814 Title: Locale issues with beta-1/2 cloud-images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/859814/+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 965551] Re: quantum-server 2012.1~rc1-0ubuntu2 fails to install
This bug was fixed in the package quantum - 2012.1~rc1-0ubuntu4 --- quantum (2012.1~rc1-0ubuntu4) precise; urgency=low * Make quantum installable again (LP: #965551): - debian/control: quantum-server depends on quantum-common. - debian/control: Add python-quantumclient dependency. - debian/upstart: Rename and update upstart job. - Fix typos in debian/quantum-common.postinst. -- Chuck ShortFri, 30 Mar 2012 14:14:42 -0400 ** Branch linked: lp:~openstack-ubuntu-testing/quantum/precise-essex- proposed ** Changed in: quantum (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to quantum in Ubuntu. https://bugs.launchpad.net/bugs/965551 Title: quantum-server 2012.1~rc1-0ubuntu2 fails to install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/quantum/+bug/965551/+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 569757] Re: NIS upstart dependency broken for lucid
I'm having numerous problems installing the -proposed package on Lucid. Sometimes the upgrade succeeds, sometimes it fails. I haven't been able to figure out why yet (I think I'm starting from the same state each time, but maybe there's a file somewhere I'm not considering). If the package upgrade WORKS: 1) I get the following output: Preparing to replace nis 3.17-31 (using .../nis_3.17-31ubuntu0.10.04.3_i386.deb) ... * Stopping NIS services [ OK ] * Stopping NIS services [ OK ] Removing any system startup links for /etc/init.d/nis ... /etc/rc1.d/K18nis /etc/rc2.d/S18nis /etc/rc3.d/S18nis /etc/rc4.d/S18nis /etc/rc5.d/S18nis Unpacking replacement nis ... Processing triggers for ureadahead ... Processing triggers for man-db ... Setting up nis (3.17-31ubuntu0.10.04.3) ... ypbind start/running, process 18583 ypserv stop/pre-start, process 18612 2) There are several upstart jobs installed in /etc/init: start-ypbind.conf, yppasswd.conf, ypserv.conf, ypxferd.conf 3) Reverting the package to the older version leaves behind the /etc/init/*yp*.conf scripts behind If the package upgrade FAILS: 1) I get the following output: Preparing to replace nis 3.17-31 (using .../nis_3.17-31ubuntu0.10.04.3_i386.deb) ... * Stopping NIS services [ OK ] * Stopping NIS services [ OK ] Removing any system startup links for /etc/init.d/nis ... /etc/rc1.d/K18nis /etc/rc2.d/S18nis /etc/rc3.d/S18nis /etc/rc4.d/S18nis /etc/rc5.d/S18nis Unpacking replacement nis ... Processing triggers for ureadahead ... Processing triggers for man-db ... Setting up nis (3.17-31ubuntu0.10.04.3) ... ypbind start/running, process 16988 start: Unknown job: ypserv invoke-rc.d: initscript ypserv, action "restart" failed. dpkg: error processing nis (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: nis E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up nis (3.17-31ubuntu0.10.04.3) ... ypbind start/running, process 17062 start: Unknown job: ypserv invoke-rc.d: initscript ypserv, action "restart" failed. dpkg: error processing nis (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: nis 2) Only one upstart jobs is installed in /etc/init: ypbind.conf 3) When I tell aptitude to revert back to the older NIS package, it leaves /etc/init/ypbind.conf behind In BOTH cases, after a server reboot, NIS doesn't come up correctly. I was able to get it working by installing (so it fails) moving the ypbind.conf file to /tmp, reverting/installing again (so it succeeds) and then moving ypbind.conf back to /etc/init. Then after a reboot it worked. ** Tags removed: verification-needed ** Tags added: verification-failed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependency broken for lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+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 859814] Re: Locale issues with beta-1/2 cloud-images
** Description changed: Default locale of image appears to be en_US.UTF-8 - however when I logon from a en_GB.UTF-8 client via SSH I get the following errors - springs up in a few places while doing things on the server. This was from a local openstack test instance; however I get the same error in ec2 instances with the latest daily snapshot. ubuntu@server-3:~$ locale locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory LANG=en_US.UTF-8 LANGUAGE= LC_CTYPE=en_GB.UTF-8 LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE=en_GB.UTF-8 LC_MONETARY="en_US.UTF-8" LC_MESSAGES=en_GB.UTF-8 LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= + Related Bugs: + * Bug 920601: cloud-images don't accept LANG settings + ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: cloud-init 0.6.1-0ubuntu15 ProcVersionSignature: User Name 3.0.0-9.15-virtual 3.0.3 Uname: Linux 3.0.0-9-virtual x86_64 Architecture: amd64 Date: Mon Sep 26 17:09:24 2011 Ec2AMI: ami-0002 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: aki-0001 Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: LC_CTYPE=en_GB.UTF-8 LC_COLLATE=en_GB.UTF-8 LANG=en_US.UTF-8 LC_MESSAGES=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: cloud-init 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/859814 Title: Locale issues with beta-1/2 cloud-images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/859814/+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 968753] Re: ssh crashed with SIGSEGV
Also occurs for me, trying to login to a host running CentOS-4 (yes I know rather old): Program received signal SIGSEGV, Segmentation fault. _vpaes_decrypt_core () at vpaes-x86.s:221 221 vpaes-x86.s: No such file or directory. (gdb) bt #0 _vpaes_decrypt_core () at vpaes-x86.s:221 #1 0xb7e369e5 in vpaes_cbc_encrypt () at vpaes-x86.s:641 #2 0x732d6361 in ?? () Many others reporting this bug. I updated the corresponding OpenSSL ticket: http://rt.openssl.org/Ticket/Display.html?id=2775 ** Bug watch added: OpenSSL RT #2775 http://rt.openssl.org/Ticket/Display.html?id=2775 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/968753 Title: ssh crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/968753/+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 959426] Re: nova + glance services die if started before db is reachable
** Changed in: nova Assignee: Adam Gandelman (gandelman-a) => Vish Ishaya (vishvananda) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/959426 Title: nova + glance services die if started before db is reachable To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/959426/+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 969431] Re: smbd crashed with SIGABRT in push_ucs2_talloc()
*** This bug is a duplicate of bug 916576 *** https://bugs.launchpad.net/bugs/916576 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #916576, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/969431/+attachment/2969380/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/969431/+attachment/2969382/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/969431/+attachment/2969383/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/969431/+attachment/2969384/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/969431/+attachment/2969385/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/969431/+attachment/2969386/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/969431/+attachment/2969387/+files/ThreadStacktrace.txt ** Visibility changed to: Public ** This bug has been marked a duplicate of private bug 916576 ** Visibility changed to: Public ** Tags removed: need-amd64-retrace -- 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/969431 Title: smbd crashed with SIGABRT in push_ucs2_talloc() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/969431/+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 969426] [NEW] Apache fails to shutdown cleanly during update and removes libapache2-mod-php5 in the process, causing service restart to fail due to syntax errors in configuration
Public bug reported: # lsb_release -rd Description:Ubuntu 10.04.4 LTS Release:10.04 # apt-cache policy apache2 apache2: Installed: 2.2.14-5ubuntu8.9 Candidate: 2.2.14-5ubuntu8.9 Version table: *** 2.2.14-5ubuntu8.9 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 100 /var/lib/dpkg/status 2.2.14-5ubuntu8.8 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid-security/main Packages 2.2.14-5ubuntu8 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages # apt-cache policy libapache2-mod-php5 libapache2-mod-php5: Installed: 5.3.2-1ubuntu4.14 Candidate: 5.3.2-1ubuntu4.14 Version table: *** 5.3.2-1ubuntu4.14 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 500 http://us.archive.ubuntu.com/ubuntu/ lucid-security/main Packages 100 /var/lib/dpkg/status 5.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages -- I have observed this behavior several times over the course of a few months now. It seems that any time I update apache2 and related packages, a) Apache cannot be shutdown cleanly, so all running processes are killed, and b) libapache2-mod-php5 is removed and never reinstalled. The fact that libapache2-mod-php5 is never reinstalled causes Apache to fail to start after the update, due to syntax errors (unrecognized directives) in the Apache configuration. The apt-get log transcript follows: -- Now updating apache2 .. Installing package(s) with command apt-get -y install apache2 .. Reading package lists... Building dependency tree... Reading state information... The following extra packages will be installed: apache2-mpm-worker apache2-threaded-dev apache2.2-bin apache2.2-common Suggested packages: ufw The following packages will be REMOVED: apache2-mpm-prefork libapache2-mod-php5 The following NEW packages will be installed: apache2-mpm-worker The following packages will be upgraded: apache2 apache2-threaded-dev apache2.2-bin apache2.2-common 4 upgraded, 1 newly installed, 2 to remove and 18 not upgraded. Need to get 3172kB of archives. After this operation, 8487kB disk space will be freed. Get:1 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main apache2-threaded-dev 2.2.14-5ubuntu8.9 [137kB] Get:2 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main apache2 2.2.14-5ubuntu8.9 [1488B] Get:3 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main apache2.2-common 2.2.14-5ubuntu8.9 [291kB] Get:4 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main apache2.2-bin 2.2.14-5ubuntu8.9 [2740kB] Get:5 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main apache2-mpm-worker 2.2.14-5ubuntu8.9 [2366B] Reading changelogs... apache2 (2.2.15-1) unstable; urgency=low * This release adds and enables mod_reqtimeout, which limits the time Apache waits for a client to send a complete request. This helps to mitigate against certain denial of service attacks. In case of problems with slow clients, the timeout values can be adjusted in /etc/apache2/mods-available/reqtimeout.conf , or the module can be disabled with "a2dismod reqtimeout". -- Chuck Short Tue, 13 Apr 2010 09:09:34 -0400 apt-listchanges: Mailing root: apt-listchanges: news for example.com Fetched 3172kB in 1s (1958kB/s) (Reading database ... 68899 files and directories currently installed.) Preparing to replace apache2-threaded-dev 2.2.14-5ubuntu8.8 (using .../apache2-threaded-dev_2.2.14-5ubuntu8.9_amd64.deb) ... Unpacking replacement apache2-threaded-dev ... Preparing to replace apache2 2.2.14-5ubuntu8.8 (using .../apache2_2.2.14-5ubuntu8.9_amd64.deb) ... Unpacking replacement apache2 ... (Reading database ... 68891 files and directories currently installed.) Removing libapache2-mod-php5 ... Module php5 disabled. Run '/etc/init.d/apache2 restart' to activate new configuration! dpkg: apache2-mpm-prefork: dependency problems, but removing anyway as you requested: roundcube-core depends on apache2 | lighttpd | httpd; however: Package apache2 is not configured yet. Package apache2-mpm-prefork which provides apache2 is to be removed. Package lighttpd is not installed. Package httpd is not installed. Package apache2-mpm-prefork which provides httpd is to be removed. mailman depends on apache2 | httpd; however: Package apache2 is not configured yet. Package apache2-mpm-prefork which provides apache2 is to be removed. Package httpd is not installed. Package apache2-mpm-prefork which provides httpd is to be removed. mediawiki depends on apache2 | httpd; however: Package apache2 is not configured yet. Package apache2-mpm-pr
[Bug 969414] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/969414/+attachment/2969260/+files/ThreadStacktrace.txt ** Changed in: apache2 (Ubuntu) Status: New => Invalid -- 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/969414 Title: apache2 crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/969414/+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 969414] Crash report cannot be processed
Thank you for your report! However, processing it in order to get sufficient information for the developers failed (it does not generate a useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report: libssl1.0.0 version 1.0.1-2ubuntu2 required, but 1.0.1-2ubuntu3 is available Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report. Thank you for your understanding, and sorry for the inconvenience! ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/969414/+attachment/2969183/+files/CoreDump.gz ** Tags removed: need-amd64-retrace -- 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/969414 Title: apache2 crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/969414/+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 969414] StacktraceTop.txt
** Attachment added: "StacktraceTop.txt" https://bugs.launchpad.net/bugs/969414/+attachment/2969259/+files/StacktraceTop.txt -- 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/969414 Title: apache2 crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/969414/+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 969414] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/969414/+attachment/2969258/+files/Stacktrace.txt -- 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/969414 Title: apache2 crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/969414/+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 969414]
-- 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/969414 Title: apache2 crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/969414/+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 969414] Re: apache2 crashed with SIGABRT in raise()
** Visibility changed to: Public -- 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/969414 Title: apache2 crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/969414/+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 859814] Re: Locale issues with beta-1/2 cloud-images
So a couple of findings here.
We are doing locales wrong: generating the locales is only part of the
process of localizations. So while Cloud-Init generates the locales, the
images are far from localized. In order to have a localized image, the
base language pack (i.e. language-pack-{en,fr,de,...} needs to be
installed otherwise the base language remains in English. The default
"en_US.UTF8" locale is incomplete in the images since the language pack
is not installed.
Therefore, I think that we should do the following:
1. The images should have the "language-pack-en" installed. Any English
speaker who is exporting variable via SSH will automatically get
localization as long as the localization is standard. Since Ubuntu's
language of collaberation is English, this should fix the vast majority
of users encountering localization problems, unless they are exporting
non-standard chacter sets (i.e. exporting en_GB instead of en_GB.UTF8).
2. Cloud-init will should support the installation of language packs
when it parses "locale: " during the cloud-config section.
3. Cloud-init should have a /etc/profile.d message that tells people if
their locale settings are wrong and how to fix it.
--
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/859814
Title:
Locale issues with beta-1/2 cloud-images
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/859814/+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 969374] [NEW] package mysql-server-5.1 5.1.58-1ubuntu1 failed to install/upgrade: ErrorMessage: subprocess new pre-removal script returned error exit status 100
Public bug reported: Had problems with 11.12 when installing lighttpd as server and packages installed or tried to install mysql, so don't think issue with 12.04 but what kind of issue do I have now after upgrading to 12.04? Thanks. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: mysql-server-5.1 5.1.58-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Fri Mar 30 11:23:09 2012 ErrorMessage: ErrorMessage: subprocess new pre-removal script returned error exit status 100 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate amd64 (20100928) SourcePackage: mysql-5.1 Title: package mysql-server-5.1 5.1.58-1ubuntu1 failed to install/upgrade: ErrorMessage: subprocess new pre-removal script returned error exit status 100 UpgradeStatus: Upgraded to precise on 2012-03-30 (0 days ago) ** Affects: mysql-5.1 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.1 in Ubuntu. https://bugs.launchpad.net/bugs/969374 Title: package mysql-server-5.1 5.1.58-1ubuntu1 failed to install/upgrade: ErrorMessage: subprocess new pre-removal script returned error exit status 100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.1/+bug/969374/+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 969374] Re: package mysql-server-5.1 5.1.58-1ubuntu1 failed to install/upgrade: ErrorMessage: subprocess new pre-removal script returned error exit status 100
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.1 in Ubuntu. https://bugs.launchpad.net/bugs/969374 Title: package mysql-server-5.1 5.1.58-1ubuntu1 failed to install/upgrade: ErrorMessage: subprocess new pre-removal script returned error exit status 100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.1/+bug/969374/+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 961232] Re: running multiple 'cobbler system reboot --name=xxx' at the same time, fence_cdu lists ALL reboots
** Package changed: fence-agents (Ubuntu) => cobbler (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cobbler in Ubuntu. https://bugs.launchpad.net/bugs/961232 Title: running multiple 'cobbler system reboot --name=xxx' at the same time, fence_cdu lists ALL reboots To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cobbler/+bug/961232/+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 961232] [NEW] running multiple 'cobbler system reboot --name=xxx' at the same time, fence_cdu lists ALL reboots
You have been subscribed to a public bug: I am running a Jenkins matrix job with four instances. Each instance will reboot the bare-metal it controls. The output of *each* fence_cdu command shows ALL systems being operated on, not only the one we are driving in this instance. example output (from a shell script run with '-x'): + ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o CheckHostIP=no -i /var/lib/ubuntu-iso-testing/kernel-sru/ssh-keys/qa-ubuntu 10.189.74.2 'sudo cobbler system reboot --name=tarf' Warning: Permanently added '10.189.74.2' (ECDSA) to the list of known hosts. task started: 2012-03-20_214707_power task started (id=Power management (reboot), time=Tue Mar 20 21:47:07 2012) cobbler power configuration is: type : sentryswitch_cdu address: 10.189.74.200 user : ubuntu id : Tarf - fence_cdu -a "10.189.74.200" -n "Tarf" -l "ubuntu" -p "ubuntu" -o "off" running: ['/bin/sh', '-c', u'fence_cdu -a "10.189.74.200" -n "Tarf" -l "ubuntu" -p "ubuntu" -o "off"'] cobbler power configuration is: type : sentryswitch_cdu address: 10.189.74.200 user : ubuntu id : Rukbah - fence_cdu -a "10.189.74.200" -n "Rukbah" -l "ubuntu" -p "ubuntu" -o "off" running: ['/bin/sh', '-c', u'fence_cdu -a "10.189.74.200" -n "Rukbah" -l "ubuntu" -p "ubuntu" -o "off"'] cobbler power configuration is: type : sentryswitch_cdu cobbler power configuration is: address: 10.189.74.200 user : ubuntu type : sentryswitch_cdu id : Alkaid - fence_cdu -a "10.189.74.200" -n "Alkaid" -l "ubuntu" -p "ubuntu" -o "off" running: ['/bin/sh', '-c', u'fence_cdu -a "10.189.74.200" -n "Alkaid" -l "ubuntu" -p "ubuntu" -o "off"'] address: 10.189.74.200 user : ubuntu id : Phact - fence_cdu -a "10.189.74.200" -n "Phact" -l "ubuntu" -p "ubuntu" -o "off" running: ['/bin/sh', '-c', u'fence_cdu -a "10.189.74.200" -n "Phact" -l "ubuntu" -p "ubuntu" -o "off"'] received on stdout: Success: Powered OFF received on stderr: received on stdout: Success: Powered OFF received on stderr: received on stdout: Success: Powered OFF received on stderr: received on stdout: Success: Powered OFF received on stderr: cobbler power configuration is: type : sentryswitch_cdu address: 10.189.74.200 user : ubuntu id : Tarf - fence_cdu -a "10.189.74.200" -n "Tarf" -l "ubuntu" -p "ubuntu" -o "on" running: ['/bin/sh', '-c', u'fence_cdu -a "10.189.74.200" -n "Tarf" -l "ubuntu" -p "ubuntu" -o "on"'] cobbler power configuration is: type : sentryswitch_cdu address: 10.189.74.200 user : ubuntu id : Alkaid - fence_cdu -a "10.189.74.200" -n "Alkaid" -l "ubuntu" -p "ubuntu" -o "on" running: ['/bin/sh', '-c', u'fence_cdu -a "10.189.74.200" -n "Alkaid" -l "ubuntu" -p "ubuntu" -o "on"'] cobbler power configuration is: type : sentryswitch_cdu address: 10.189.74.200 user : ubuntu id : Rukbah - fence_cdu -a "10.189.74.200" -n "Rukbah" -l "ubuntu" -p "ubuntu" -o "on" running: ['/bin/sh', '-c', u'fence_cdu -a "10.189.74.200" -n "Rukbah" -l "ubuntu" -p "ubuntu" -o "on"'] cobbler power configuration is: type : sentryswitch_cdu address: 10.189.74.200 user : ubuntu id : Phact - fence_cdu -a "10.189.74.200" -n "Phact" -l "ubuntu" -p "ubuntu" -o "on" running: ['/bin/sh', '-c', u'fence_cdu -a "10.189.74.200" -n "Phact" -l "ubuntu" -p "ubuntu" -o "on"'] received on stdout: Success: Powered ON received on stderr: *** TASK COMPLETE *** ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: fence-agents (not installed) ProcVersionSignature: Ubuntu 3.0.0-16.28-server 3.0.17 Uname: Linux 3.0.0-16-server x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Wed Mar 21 14:26:24 2012 SourcePackage: fence-agents UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cobbler (Ubuntu) Importance: Undecided Assignee: Canonical Server Team (canonical-server) Status: New ** Tags: amd64 apport-bug oneiric qa-manual-testing -- running multiple 'cobbler system reboot --name=xxx' at the same time, fence_cdu lists ALL reboots https://bugs.launchpad.net/bugs/961232 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cobbler in Ubuntu. -- 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 966566] Re: create/document charm store review process
The policy and process are documented here: https://juju.ubuntu.com/Charms I added a recommendation to use AppArmor: "should make use of AppArmor to increase security" ** Changed in: juju (Ubuntu Precise) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/966566 Title: create/document charm store review process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/966566/+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 969228] Re: Unable to load another apparmor profile from /etc/apparmor.d/lxc/
** Attachment added: "lxc-upgrader01" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/969228/+attachment/2968175/+files/lxc-upgrader01 -- 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/969228 Title: Unable to load another apparmor profile from /etc/apparmor.d/lxc/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/969228/+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 969228] Re: Unable to load another apparmor profile from /etc/apparmor.d/lxc/
** Attachment added: "lxc-default" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/969228/+attachment/2968171/+files/lxc-default -- 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/969228 Title: Unable to load another apparmor profile from /etc/apparmor.d/lxc/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/969228/+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 962507] Re: [FFE] Latest juju snapshot enables maas provider
Having tested the PPA version extensively this last week, in relation to what this bug is addressing; I am happy for an upload which closely resembles what has been in the PPA to be uploaded. Thanks. FFe ACK, please upload. Thanks ** Changed in: juju (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/962507 Title: [FFE] Latest juju snapshot enables maas provider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/962507/+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 969228] Re: Unable to load another apparmor profile from /etc/apparmor.d/lxc/
Hi, can you attach the profiles in question? That will help in diagnosing the issue. -- 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/969228 Title: Unable to load another apparmor profile from /etc/apparmor.d/lxc/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/969228/+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 969228] Re: Unable to load another apparmor profile from /etc/apparmor.d/lxc/
If I pull the #include from both container profiles and put it at top of /etc/apparmor.d/lxc-containers, then it works. I don't want to lose the ability for users to load just a new container profile. But as there's on #ifdef I can trigger the #include on, perhaps it's best to tell users to either /etc/init.d/apparmor reload, or apparmor_parser -r /etc/apparmor.d/lxc-containers. ** Changed in: lxc (Ubuntu) Status: Incomplete => Confirmed ** Changed in: apparmor (Ubuntu) Status: Incomplete => Invalid -- 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/969228 Title: Unable to load another apparmor profile from /etc/apparmor.d/lxc/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/969228/+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 969228] Re: Unable to load another apparmor profile from /etc/apparmor.d/lxc/
Oh, this might be my fault. If you remove the #include from your new profile, does that work? ** Changed in: apparmor (Ubuntu) Importance: Undecided => High ** Changed in: lxc (Ubuntu) Importance: Undecided => High ** Changed in: lxc (Ubuntu) Status: New => Incomplete ** Changed in: apparmor (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/969228 Title: Unable to load another apparmor profile from /etc/apparmor.d/lxc/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/969228/+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 969228] Re: Unable to load another apparmor profile from /etc/apparmor.d/lxc/
Also opening against apparmor as it's not clear whether it's lxc's or apparmor's fault. ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/969228 Title: Unable to load another apparmor profile from /etc/apparmor.d/lxc/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/969228/+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 969228] [NEW] Unable to load another apparmor profile from /etc/apparmor.d/lxc/
Public bug reported:
I'm trying to set another apparmor profile for a specific container, so
I set lxc.aa_profile to lxc-upgrader01 and simply copied the default
profile for now, but when reloading apparmor it fails...
=
root@athos:/etc/apparmor.d/lxc# ls
lxc-default
root@athos:/etc/apparmor.d/lxc# /etc/init.d/apparmor reload
* Reloading AppArmor profiles
Skipping profile in /etc/apparmor.d/disable: sbin.dhclient
Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
[ OK ]
root@athos:/etc/apparmor.d/lxc# dmesg -c
[123440.717875] type=1400 audit(1333115077.171:102): apparmor="STATUS"
operation="profile_replace" name="/usr/bin/lxc-start" pid=19479
comm="apparmor_parser"
[123440.743692] type=1400 audit(1333115077.195:103): apparmor="STATUS"
operation="profile_replace" name="lxc-container-default" pid=19477
comm="apparmor_parser"
[123440.908215] type=1400 audit(1333115077.363:104): apparmor="STATUS"
operation="profile_replace" name="/usr/sbin/ntpd" pid=19480
comm="apparmor_parser"
[123440.947041] type=1400 audit(1333115077.399:105): apparmor="STATUS"
operation="profile_replace" name="/usr/sbin/tcpdump" pid=19482
comm="apparmor_parser"
root@athos:/etc/apparmor.d/lxc# mv /root/lxc-upgrader01 .
root@athos:/etc/apparmor.d/lxc# diff -Nrup lxc-default lxc-upgrader01
--- lxc-default 2012-03-30 13:38:30.966724366 +
+++ lxc-upgrader01 2012-03-30 13:38:49.389578258 +
@@ -1,6 +1,7 @@
#include
-profile lxc-container-default flags=(attach_disconnected) {
+profile lxc-container-upgrader01 flags=(attach_disconnected) {
+
network,
capability,
file,
root@athos:/etc/apparmor.d/lxc# /etc/init.d/apparmor reload
* Reloading AppArmor profiles
Skipping profile in /etc/apparmor.d/disable: sbin.dhclient
AppArmor parser error for /etc/apparmor.d/lxc-containers in
/etc/apparmor.d/tunables/home at line 16: syntax error, unexpected TOK_SET_VAR,
expecting TOK_ID
Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
[fail]
root@athos:/etc/apparmor.d/lxc# dmesg -c
[123465.749549] type=1400 audit(1333115102.202:106): apparmor="STATUS"
operation="profile_replace" name="/usr/bin/lxc-start" pid=20414
comm="apparmor_parser"
[123465.968228] type=1400 audit(1333115102.422:107): apparmor="STATUS"
operation="profile_replace" name="/usr/sbin/ntpd" pid=20415
comm="apparmor_parser"
[123465.984424] type=1400 audit(1333115102.438:108): apparmor="STATUS"
operation="profile_replace" name="/usr/sbin/tcpdump" pid=20421
comm="apparmor_parser"
[123466.025319] type=1400 audit(1333115102.478:109): apparmor="STATUS"
operation="profile_remove" name="lxc-container-default" pid=20561
comm="apparmor"
root@athos:/etc/apparmor.d/lxc# ls
lxc-default lxc-upgrader01
root@athos:/etc/apparmor.d/lxc#
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/969228
Title:
Unable to load another apparmor profile from /etc/apparmor.d/lxc/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/969228/+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 861459] Re: /etc/nova/nova-compute.conf not owned by nova
** Branch linked: lp:~openstack-ubuntu-testing/nova/precise-essex- proposed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/861459 Title: /etc/nova/nova-compute.conf not owned by nova To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/861459/+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 960276] Re: a bad AMI can hang an entire compute node
** Changed in: nova (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/960276 Title: a bad AMI can hang an entire compute node To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/960276/+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 942646] Re: No logrotate files for nova-manage and nova-dhcbridge
** Changed in: nova (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/942646 Title: No logrotate files for nova-manage and nova-dhcbridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/942646/+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 942646] Re: No logrotate files for nova-manage and nova-dhcbridge
** Branch linked: lp:~openstack-ubuntu-testing/nova/precise-essex- proposed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/942646 Title: No logrotate files for nova-manage and nova-dhcbridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/942646/+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 948461] Re: apt-get hashsum/size mismatch because s3 mirrors don't support http pipelining correctly
This bug was fixed in the package cloud-init - 0.5.15-0ubuntu3.1 --- cloud-init (0.5.15-0ubuntu3.1) maverick-proposed; urgency=low * add ability to configure Acquire::http::Pipeline-Depth via cloud-config setting 'apt_pipelining' (LP: #948461) * debian/cloud-init.postinst: address population of apt_pipeline setting on installation. -- Scott MoserFri, 16 Mar 2012 14:36:07 -0400 -- 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/948461 Title: apt-get hashsum/size mismatch because s3 mirrors don't support http pipelining correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/948461/+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 948461] Re: apt-get hashsum/size mismatch because s3 mirrors don't support http pipelining correctly
This bug was fixed in the package cloud-init - 0.6.1-0ubuntu22.1 --- cloud-init (0.6.1-0ubuntu22.1) oneiric-proposed; urgency=low * add ability to configure Acquire::http::Pipeline-Depth via cloud-config setting 'apt_pipelining' (LP: #948461) * debian/cloud-init.postinst: address population of apt_pipeline setting on installation. -- Ben HowardFri, 16 Mar 2012 15:44:50 -0600 ** Changed in: cloud-init (Ubuntu Maverick) Status: Fix Committed => Fix Released -- 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/948461 Title: apt-get hashsum/size mismatch because s3 mirrors don't support http pipelining correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/948461/+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 948461] Re: apt-get hashsum/size mismatch because s3 mirrors don't support http pipelining correctly
This bug was fixed in the package cloud-init - 0.6.1-0ubuntu8.1 --- cloud-init (0.6.1-0ubuntu8.1) natty-proposed; urgency=low * add ability to configure Acquire::http::Pipeline-Depth via cloud-config setting 'apt_pipelining' (LP: #948461) * debian/cloud-init.postinst: address population of apt_pipeline setting on installation. -- Ben HowardFri, 16 Mar 2012 11:05:48 -0600 ** Changed in: cloud-init (Ubuntu Oneiric) Status: Fix Committed => Fix Released -- 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/948461 Title: apt-get hashsum/size mismatch because s3 mirrors don't support http pipelining correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/948461/+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 948461] Re: apt-get hashsum/size mismatch because s3 mirrors don't support http pipelining correctly
This bug was fixed in the package cloud-init - 0.5.10-0ubuntu1.7 --- cloud-init (0.5.10-0ubuntu1.7) lucid-proposed; urgency=low * add ability to configure Acquire::http::Pipeline-Depth via cloud-config setting 'apt_pipelining' (LP: #948461) * debian/cloud-init.postinst: address population of apt_pipeline setting on installation. -- Scott MoserFri, 16 Mar 2012 14:32:50 -0400 ** Changed in: cloud-init (Ubuntu Lucid) Status: Fix Committed => Fix Released ** Changed in: cloud-init (Ubuntu Natty) Status: Fix Committed => Fix Released -- 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/948461 Title: apt-get hashsum/size mismatch because s3 mirrors don't support http pipelining correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/948461/+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 968983] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/968983/+attachment/2965999/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/968983/+attachment/2965958/+files/CoreDump.gz ** Changed in: openssh (Ubuntu) Importance: Undecided => Medium ** Tags removed: need-i386-retrace -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/968983 Title: ssh crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/968983/+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 968983] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/968983/+attachment/2965998/+files/Stacktrace.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/968983 Title: ssh crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/968983/+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 968983]
StacktraceTop: _vpaes_decrypt_core () at vpaes-x86.s:221 vpaes_cbc_encrypt () at vpaes-x86.s:641 ?? () -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/968983 Title: ssh crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/968983/+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 968983] Re: ssh crashed with SIGSEGV
** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/968983 Title: ssh crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/968983/+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
