[Bug 1181334] Re: i386 required to install amd64
** Changed in: maas Assignee: (unassigned) = Tycho Andersen (tycho-s) -- 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/1181334 Title: i386 required to install amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1181334/+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 1253884] Re: package mysql-server-core-5.5 5.5.32-0ubuntu0.12.04.1 failed to install/upgrade: short read on buffer copy for backend dpkg-deb during `./usr/sbin/mysqld'
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the update again. This will likely resolve your issue, but the failure could be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. Thanks in advance! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: short-read ** Changed in: mysql-5.5 (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.5 in Ubuntu. https://bugs.launchpad.net/bugs/1253884 Title: package mysql-server-core-5.5 5.5.32-0ubuntu0.12.04.1 failed to install/upgrade: short read on buffer copy for backend dpkg-deb during `./usr/sbin/mysqld' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1253884/+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 1253940] Re: The parameters for the ipmi_si kernel module need to be tweaked for IPMI detection to work on certain hardware.
We need to investigate the possibility of having a list of parameters for the ipmi_si kernel module and try doing the IPMI detection for all these parameters in sequence. ** Also affects: maas-enlist (Ubuntu) Importance: Undecided Status: New ** Changed in: maas Milestone: None = 14.04 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas-enlist in Ubuntu. https://bugs.launchpad.net/bugs/1253940 Title: The parameters for the ipmi_si kernel module need to be tweaked for IPMI detection to work on certain hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1253940/+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 1224517] Re: please add glusterfs support
Hi, I'm on 13.10 and did the following to get glusterfs support in qemu. == Install GlusterFS PPA Add PPA repo from semiosis sudo add-apt-repository ppa:semiosis/ubuntu-glusterfs-3.4 sudo apt-get update sudo apt-get -y install glusterfs-client glusterfs-server == Get GlusterFS glfs.h wget http://download.gluster.org/pub/gluster/glusterfs/3.4/LATEST/glusterfs-3.4.1.tar.gz tar xzf glusterfs* mkdir -p /usr/include/glusterfs/api/ cp glusterfs*/api/src/glfs.h /usr/include/glusterfs/api/ rm -rf glusterfs* == Rebuild qemu deb mkdir rebuild-qemu cd rebuild-qemu apt-get source qemu sudo apt-get -y build-dep qemu cd qemu* sed -i -e '/^XSBC-Original-Maintainer/d' -e 's/Maintainer/XSBC-Original-Maintainer/' -e '4iMaintainer: minime min...@maxime.xx ' debian/control dch -l custom dch -r saucy sed '3iDEB_CONFIGURE_EXTRA_FLAGS=--enable-glusterfs' debian/rules debuild -us -uc -j$(($(grep processor /proc/cpuinfo |wc -l) + 2)) Put this devs in you own repo and install them :) -- 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/1224517 Title: please add glusterfs support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1224517/+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 893978] Re: Groovy package should depend on either sun-jdk or openjdk
Where do you get the sun-jdk package? Is it generated using java- package? AFAIK the package is removed, and Oracle only provides rpm and binary installers. Anyway, this bug should be filed here: https://launchpad.net/ubuntu/+source/java-common/+filebug as that is the source of the default-jdk package. ** Changed in: groovy (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to groovy in Ubuntu. https://bugs.launchpad.net/bugs/893978 Title: Groovy package should depend on either sun-jdk or openjdk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/groovy/+bug/893978/+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 1247299] Re: local provider deploys fail with 'install hook failed'
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1247299 Title: local provider deploys fail with 'install hook failed' To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1247299/+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 1240709] Re: local provider fails to start
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1240709 Title: local provider fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1240709/+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 1243861] Re: juju should add the cloud-archive repository differently
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1243861 Title: juju should add the cloud-archive repository differently To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1243861/+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 1240927] Re: os.rename does not work with windows
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1240927 Title: os.rename does not work with windows To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1240927/+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-1311-juju] Juju activities for Trusty
Blueprint changed by James Page: Work items changed: Work items for ubuntu-13.11: SRU for juju-core 1.16.3 into saucy: INPROGRESS Work items for ubuntu-13.12: - Completion of juju-core porting to gccgo: TODO Testing with gccgo in upstream CI: TODO Testing of juju-core of gccgo early in cycle: TODO Work items for ubuntu-14.01: Update juju-core to 2.x release: TODO Split shared go dependencies from juju-core source package: TODO MIR juju-mongodb: TODO MIR juju-core: TODO MIR juju-core dependencies: TODO Work items for ubuntu-14.04: MRE for juju-core: TODO -- Juju activities for Trusty https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1311-juju -- 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 1245004] Re: Relation names regex too restrictive
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1245004 Title: Relation names regex too restrictive To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1245004/+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 1241666] Re: Cannot create simple streams for Ubuntu trusty series
Confirmed that I can sync trusty tools using 1.16.3. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1241666 Title: Cannot create simple streams for Ubuntu trusty series To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1241666/+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 1246556] Re: lxc containers broken with maas
Confirmed able to add LXC containers to physical servers using this update. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1246556 Title: lxc containers broken with maas To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1246556/+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 1229275] Re: [maas] juju destroy-environment also destroys nodes that are not controlled by juju
Confirmed that destroying an environment only destroys machines allocated to that environment ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1229275 Title: [maas] juju destroy-environment also destroys nodes that are not controlled by juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1229275/+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 1081247] Re: maas provider releases all nodes it did not allocate [does not play well with others]
Confirmed that destroying an environment only terminates machines allocated to that environment; namespacing looks good ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1081247 Title: maas provider releases all nodes it did not allocate [does not play well with others] To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1081247/+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 1240423] Re: provider/maas: environment-uuid is the wrong name to use for the machine disambiguation tag
General testing of MAAS+Juju completed OK. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1240423 Title: provider/maas: environment-uuid is the wrong name to use for the machine disambiguation tag To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1240423/+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 1253987] [NEW] maas-enlist detects midway as generic-lpae instead of highbank
Public bug reported: The conclusion, at least for now, is that midway machines should be reported to MAAS as highbank, not generic-lpae as it currently does in Saucy. ** Affects: maas-enlist (Ubuntu) Importance: Undecided Status: New ** Tags: midway -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas-enlist in Ubuntu. https://bugs.launchpad.net/bugs/1253987 Title: maas-enlist detects midway as generic-lpae instead of highbank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas-enlist/+bug/1253987/+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 1253990] [NEW] sessions removed even if max life time isn't reached
Public bug reported: It seems that the script /usr/lib/php5/maxlifetime does not recognize settings that are done in the new conf.d structure. Just only the original php.ini is read. In my special case the setting of session.gc_maxlifetime is done in as special file conf.d/sessions.ini which is ignored. ** Affects: php5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1253990 Title: sessions removed even if max life time isn't reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1253990/+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 1253990] Re: sessions removed even if max life time isn't reached
The Server is Saucy Salamander (13.10). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1253990 Title: sessions removed even if max life time isn't reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1253990/+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 1246320] Re: Azure bootstrap fails: versioning header is not specified
2013-11-22 12:17:57 INFO juju.state open.go:106 connection established
environment: azure
machines:
0:
agent-state: started
agent-version: 1.16.3
dns-name: juju-azure-3qam297c0t.cloudapp.net
instance-id: juju-azure-3qam297c0t
instance-state: Created
series: precise
services: {}
2013-11-22 12:18:05 INFO juju supercommand.go:286 command finished
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1246320
Title:
Azure bootstrap fails: versioning header is not specified
To manage notifications about this bug go to:
https://bugs.launchpad.net/gwacl/+bug/1246320/+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 1205875] Re: apparmor.d profile for usr.sbin.ntpd -- access to samba gencache and capability block_suspend
** Changed in: ntp (Ubuntu) Importance: Undecided = Low ** Changed in: ntp (Ubuntu) Status: Expired = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1205875 Title: apparmor.d profile for usr.sbin.ntpd -- access to samba gencache and capability block_suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1205875/+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 1253669] Re: unable to launch lxc application containers when dropping cap_sysadmin
I've been trying to narrow it down by running lxc-execute on a few other systems, including a 12.04.3 with the 3.2.0-55-generic Kernel, no success. As you said, the debug output unfortunately does not provide any details. What I know so far: * lxc 0.7.5-3 (standard precise version) and 0.8.0~rc1 (backport) work fine on 3.2 and 3.8 kernels * as soon as I upgrade to 1.0.0~alpha1 and any kernel, it does not work anymore * upgrading to the latest daily (1.0.0~alpha3+master~20131122-0500-0ubuntu1~ppa1~precise1) does not resolve the issue on 3.2 and 3.8 I also tried to use a custom container (see attached lxc configuration) using # lxc-execute -n foo -f lxc.conf -- /bin/bash, but no luck. Note that I run lxc-execute directly from the command line on the host, not inside a OS container. FYI: I use lxc to isolate Apache2 instances on my webservers, using complex container setups with my own templates. As I said, this worked perfectly with 0.8.0~rc1 and earlier, and with 1.0.0~alpha1 the containers work as well - except it is impossible to drop cap_sys_admin. ** Attachment added: lxc configuration https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1253669/+attachment/3915022/+files/lxc_foo.txt -- 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/1253669 Title: unable to launch lxc application containers when dropping cap_sysadmin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1253669/+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 1253669] Re: unable to launch lxc application containers when dropping cap_sysadmin
Quoting Sebastian Wendland (wendl...@cg.uni-saarland.de): I've been trying to narrow it down by running lxc-execute on a few other systems, including a 12.04.3 with the 3.2.0-55-generic Kernel, no success. As you said, the debug output unfortunately does not provide any details. Could you try installing strace in the container and running bash under strace -f -o/debug.out ? -- 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/1253669 Title: unable to launch lxc application containers when dropping cap_sysadmin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1253669/+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 1253847] Re: Sync libcommons-fileupload-java 1.3-2.1 (universe) from Debian unstable (main)
Yeah, that's right. I was trying to build another .dsc file. However, there is not so much benefit in Debian, so I'm not going to investigate where's the problem. I'm unsubscribing ubuntu-sponsors for now. Feel free someone to fix it. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libcommons-fileupload-java in Ubuntu. https://bugs.launchpad.net/bugs/1253847 Title: Sync libcommons-fileupload-java 1.3-2.1 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcommons-fileupload-java/+bug/1253847/+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-1311-seeded-package-review] Server Seeded Package review
Blueprint changed by James Page: Definition Status: Approved = Review -- Server Seeded Package review https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1311-seeded-package-review -- 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-1311-seeded-package-review] Server Seeded Package review
Blueprint changed by James Page: Work items changed: Work items for ubuntu-13.12: Generate list of potential removal candidates and circulate on -devel, -server, -cloud for review: TODO Review dm-cache/bcache for main inclusion: TODO - Work items for ubuntu-14.02: + Work items: Remove agreed candidates from seeds: TODO -- Server Seeded Package review https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1311-seeded-package-review -- 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-1311-ceph] Ceph activities for Trusty
Blueprint changed by James Page: Whiteboard changed: [UDS DISCUSSION TOPICS] - Ceph release targets for 14.04 - assumed firefly - RADOS Gateway geo-replication packaging (missed for saucy) - Support Ceph for a 5 year LTS release - whats the plan? - Charm updates - whats needed. - mod_fastcgi multiverse-main (fully supported RADOS Gateway) - ceph-deploy. + http://pad.ubuntu.com/uds-1311-servercloud-1311-ceph [USER STORIES] John is deploying Ceph with OpenStack Icehouse; he's able to leverage the latest Ceph integration features using Ceph directly from the Ubuntu Archive. Tony wants to deploy a geo-replicated RADOS Gateway on Ceph; he's able todo this using Ceph from the Ubuntu Archive. [ASSUMPTIONS] Firefly release schedule lines up with Ubuntu release schedule. [RISKS] Ceph is not really supportable for a 5 year LTS (mitigation - provision of newer Ceph in Cloud Archive for 14.04). [IN SCOPE] Charms Packages [OUT OF SCOPE] - [USER ACCEPTANCE] - [RELEASE NOTE/BLOG] Ubuntu 14.04 includes the latest stable release of Ceph, providing massively scalable object and block storage services. -- Ceph activities for Trusty https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1311-ceph -- 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-1311-ceph] Ceph activities for Trusty
Blueprint changed by James Page: Work items changed: Work items for ubuntu-13.11: Update ceph packages for emperor upstream release: DONE - Re-sync packaging with Debian: TODO + Re-sync packaging with Debian: INPROGRESS Work items for ubuntu-13.12: Package geo-replication agents for RADOS gateway: TODO Review/move mod_fastcgi out of multiverse: TODO MIR mod_fastcgi: TODO Work items for ubuntu-14.01: Fully automated testing of ceph for SRU's and development release: TODO Work items for ubuntu-14.04: Updates to charms for Ceph firefly: TODO - Update ceph packages for firefly upstream release: TODO -- Ceph activities for Trusty https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1311-ceph -- 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-1311-ceph] Ceph activities for Trusty
Blueprint changed by James Page: Whiteboard changed: [UDS DISCUSSION TOPICS] http://pad.ubuntu.com/uds-1311-servercloud-1311-ceph [USER STORIES] John is deploying Ceph with OpenStack Icehouse; he's able to leverage the latest Ceph integration features using Ceph directly from the Ubuntu Archive. Tony wants to deploy a geo-replicated RADOS Gateway on Ceph; he's able todo this using Ceph from the Ubuntu Archive. [ASSUMPTIONS] Firefly release schedule lines up with Ubuntu release schedule. [RISKS] Ceph is not really supportable for a 5 year LTS (mitigation - provision of newer Ceph in Cloud Archive for 14.04). [IN SCOPE] Charms Packages [OUT OF SCOPE] [USER ACCEPTANCE] [RELEASE NOTE/BLOG] - Ubuntu 14.04 includes the latest stable release of Ceph, providing massively scalable object and block storage services. + Ubuntu 14.04 includes the latest stable release of Ceph, providing massively scalable object and block storage services. New features in this release include Erasure encoding of objects and tiered storage pools. -- Ceph activities for Trusty https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1311-ceph -- 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-1311-ceph] Ceph activities for Trusty
Blueprint changed by James Page: Work items changed: Work items for ubuntu-13.11: Update ceph packages for emperor upstream release: DONE Re-sync packaging with Debian: INPROGRESS Work items for ubuntu-13.12: Package geo-replication agents for RADOS gateway: TODO Review/move mod_fastcgi out of multiverse: TODO MIR mod_fastcgi: TODO Work items for ubuntu-14.01: Fully automated testing of ceph for SRU's and development release: TODO - Work items for ubuntu-14.02: - Update ceph packages for firefly release: TODO - Work items for ubuntu-14.04: Updates to charms for Ceph firefly: TODO - Ceph REST API - integrate option into charms/packaging: TODO - Update ceph packages for firefly upstream point release: TODO -- Ceph activities for Trusty https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1311-ceph -- 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-1311-ceph] Ceph activities for Trusty
Blueprint changed by James Page: Definition Status: New = Review -- Ceph activities for Trusty https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1311-ceph -- 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 1253669] Re: unable to launch lxc application containers when dropping cap_sysadmin
Here is the strace for # strace -f -o/debug.out lxc-execute -o foo -l DEBUG -s lxc.cap.drop=sys_admin -n foo -- /bin/bash using lxc 1.0.0.alpha3 on 3.8.0-33 kernel ** Attachment added: debug.out https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1253669/+attachment/3915061/+files/debug.out -- 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/1253669 Title: unable to launch lxc application containers when dropping cap_sysadmin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1253669/+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 1254085] [NEW] ssh fails to connect to VPN host - hangs at 'expecting SSH2_MSG_KEX_ECDH_REPLY'
Public bug reported: ssh -vvv host is failing for me where host is a VPN system. VPN is configured and connected via network-manager. Last messages from ssh (hangs forever): debug2: kex_parse_kexinit: none,z...@openssh.com debug2: kex_parse_kexinit: none,z...@openssh.com debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: mac_setup: found hmac-md5 debug1: kex: server-client aes128-ctr hmac-md5 none debug2: mac_setup: found hmac-md5 debug1: kex: client-server aes128-ctr hmac-md5 none debug1: sending SSH2_MSG_KEX_ECDH_INIT debug1: expecting SSH2_MSG_KEX_ECDH_REPLY = Workaround = $ sudo apt-get install putty $ putty host This works perfectly. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: openssh-client 1:6.4p1-1 ProcVersionSignature: Ubuntu 3.12.0-3.8-generic 3.12.0 Uname: Linux 3.12.0-3-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.7-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Fri Nov 22 15:37:18 2013 InstallationDate: Installed on 2010-10-21 (1128 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) RelatedPackageVersions: ssh-askpass 1:1.2.4.1-9 libpam-sshN/A keychain 2.7.1-1 ssh-askpass-gnome 1:6.4p1-1 SSHClientVersion: OpenSSH_6.4p1 Ubuntu-1, OpenSSL 1.0.1e 11 Feb 2013 SourcePackage: openssh UpgradeStatus: Upgraded to trusty on 2013-11-01 (20 days ago) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- 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/1254085 Title: ssh fails to connect to VPN host - hangs at 'expecting SSH2_MSG_KEX_ECDH_REPLY' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1254085/+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 1223010] Re: Use oauthlib rather than oauth2
Not sure if we want to merge these two bugs or not, but upstream this issue is tracked in bug 1240382 ** Summary changed: - Use oauthlib rather than oauth. + Use oauthlib rather than oauth2 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/1223010 Title: Use oauthlib rather than oauth2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/1223010/+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 1236439] Re: switch to use hostnames like nova breaks upgrades of l3-agent
I don't think this issue will be that simple to fix. In order to provide a helper script we would need to have the script access all of the machines to determine their hostname and fqdn. If one wants to avoid this one could write a script to gather this data and then update the db with this data. That said I think it will be hard for us to provide a shrink warp script to solve this issue as unfortunate as it is. Also fwiw on all of my machines my hostnames just happen to be the same as the fqdn. If someone does want to work on this though I definitely would support that effort. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1236439 Title: switch to use hostnames like nova breaks upgrades of l3-agent To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1236439/+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 1223010] Re: Use oauthlib rather than oauth2
Dolph, This is a tracking a bug we have in Ubuntu for it. chuck -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/1223010 Title: Use oauthlib rather than oauth2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/1223010/+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 1253669] Re: unable to launch lxc application containers when dropping cap_sysadmin
Plus the lxc-execute debug output for the same command ** Attachment added: foo https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1253669/+attachment/3915063/+files/foo -- 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/1253669 Title: unable to launch lxc application containers when dropping cap_sysadmin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1253669/+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 1254090] Re: package libapache2-mod-auth-plain 2.0.52 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libapache2-mod-auth-plain in Ubuntu. https://bugs.launchpad.net/bugs/1254090 Title: package libapache2-mod-auth-plain 2.0.52 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libapache2-mod-auth-plain/+bug/1254090/+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 1254090] [NEW] package libapache2-mod-auth-plain 2.0.52 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
Public bug reported: I was doing an upgrade to 13.10 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libapache2-mod-auth-plain 2.0.52 ProcVersionSignature: Ubuntu 3.2.0-56.86-generic 3.2.51 Uname: Linux 3.2.0-56-generic i686 ApportVersion: 2.12.7-0ubuntu1 Architecture: i386 Date: Thu Nov 21 14:18:33 2013 Dependencies: gcc-4.8-base 4.8.2-1ubuntu2 libc6 2.17-93ubuntu4 libgcc1 1:4.8.2-1ubuntu2 multiarch-support 2.17-93ubuntu4 DuplicateSignature: package:libapache2-mod-auth-plain:2.0.52:ErrorMessage: subprocess installed post-installation script returned error exit status 1 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 SourcePackage: libapache2-mod-auth-plain Title: package libapache2-mod-auth-plain 2.0.52 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to trusty on 2013-11-22 (0 days ago) ** Affects: libapache2-mod-auth-plain (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libapache2-mod-auth-plain in Ubuntu. https://bugs.launchpad.net/bugs/1254090 Title: package libapache2-mod-auth-plain 2.0.52 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libapache2-mod-auth-plain/+bug/1254090/+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 1253669] Re: unable to launch lxc application containers when dropping cap_sysadmin
I actually meant to run strace under lxc-execute, but this was also helpful. Could you please add a proc entry to your lxc.mount.entry lines in the container configuration, and see whether that helps? -- 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/1253669 Title: unable to launch lxc application containers when dropping cap_sysadmin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1253669/+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 1253669] Re: unable to launch lxc application containers when dropping cap_sysadmin
Running strace inside lxc-execute (i.e. lxc-execute -n foo -s lxc.cap.drop=sys_admin -- strace -f -o/root/debug.out /bin/bash) does not work as strace will immediately crash just like bash, thus producing no output. Here is the lxc log for # lxc-execute -n foo -f lxc.conf -o foo -l DEBUG -- /bin/bash with the lxc config below (again on 3.8 with the daily lxc build). lxc.utsname = foo lxc.cap.drop = sys_admin lxc.tty = 1 lxc.console=/lxc/foo/console lxc.rootfs = /lxc/foo/rootfs lxc.mount.entry = /usr usr nonero,bind 0 0 lxc.mount.entry = /lib lib nonero,bind 0 0 lxc.mount.entry = /lib64lib64 nonero,bind 0 0 lxc.mount.entry = /bin bin nonero,bind 0 0 lxc.mount.entry = /sbin sbin nonero,bind 0 0 lxc.mount.entry = /lxc/dev/null dev/null nonebind0 0 lxc.mount.entry = /lxc/dev/zero dev/zero nonebind0 0 lxc.mount.entry = /lxc/dev/random dev/random nonebind0 0 lxc.mount.entry = /lxc/dev/urandom dev/urandom nonebind0 0 lxc.mount.entry = tmpfs tmp tmpfs rw,size=100M,noexec,nodev,mode=1777 0 0 lxc.mount.entry = proc proc procnodev,noexec,nosuid 0 0 ** Attachment added: lxc-execute debug output https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1253669/+attachment/3915084/+files/lxc_debug -- 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/1253669 Title: unable to launch lxc application containers when dropping cap_sysadmin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1253669/+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 1254111] [NEW] MAAS tft server lacks uEFI netboot files.
Public bug reported: The MAAS' TFT Server lacks the UEFI netboot files and support. ** Affects: maas (Ubuntu) Importance: Undecided Assignee: Andres Rodriguez (andreserl) Status: Triaged ** Changed in: maas (Ubuntu) Assignee: (unassigned) = Andres Rodriguez (andreserl) ** Changed in: maas (Ubuntu) Status: New = Triaged ** Description changed: - The MAAS' TFT Server lacks the UEFI netboot files. Work should be made - to install these. + The MAAS' TFT Server lacks the UEFI netboot files and 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/1254111 Title: MAAS tft server lacks uEFI netboot files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1254111/+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 1253669] Re: unable to launch lxc application containers when dropping cap_sysadmin
Oh, now I see. lxc-init calls setup_fs() which fails if it cannot mount proc. (I had looked for direct calls to mount proc but missed the setup_fs call) Without cap_sys_admin you cannot mount proc. What's unclear to me now is why this would have worked for you with older lxc. This is not something that has recently changed, so it should have always failed. I think updating lxc-init to only warn if you could not mount /proc would be good. Will send a patch upstream for that and see if anyone can think of a good counter argument. status: confirmed importance: medium ** Changed in: lxc (Ubuntu) Importance: Undecided = Medium ** Changed in: lxc (Ubuntu) Status: Incomplete = 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/1253669 Title: unable to launch lxc application containers when dropping cap_sysadmin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1253669/+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 1159748] Re: Random apache2 crash in Ubuntu 12.04 (libpthread-2.15.so)
** Summary changed: - Ramdom apache2 crash in Ubuntu 12.04 (libpthread-2.15.so) + Random apache2 crash in Ubuntu 12.04 (libpthread-2.15.so) -- 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/1159748 Title: Random apache2 crash in Ubuntu 12.04 (libpthread-2.15.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1159748/+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 1253669] Re: unable to launch lxc application containers when dropping cap_sysadmin
Fix pushed to git. ** Changed in: lxc (Ubuntu) Status: Confirmed = Fix Committed -- 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/1253669 Title: unable to launch lxc application containers when dropping cap_sysadmin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1253669/+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 1253669] Re: unable to launch lxc application containers when dropping cap_sysadmin
** Also affects: lxc (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: lxc (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: lxc (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: lxc (Ubuntu Raring) 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/1253669 Title: unable to launch lxc application containers when dropping cap_sysadmin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1253669/+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 1253669] Re: unable to launch lxc application containers when dropping cap_sysadmin
** Description changed: + + SRU Justification + 1. Impact: cannot lxc-execute a container without cap_sys_admin + 2. Development fix: don't fail if lxc-init cannot mount /proc + 3. Stable fix: same as development fix. + 4. Test case: + 5. Regression potential: none + + Using the 0.8.0~rc1 lxc release, it was possible to start an application container with the lxc.cap.drop=sys_admin option (# lxc-execute -n foo -s lxc.cap.drop=sys_admin -- /bin/bash). Since the new 1.0.0~alpha1 release, this is not possible anymore; the application immediately crashes upon being called by lxc-init, thus killing the container. When any other capability (or combination of capabilities) is dropped, the container still starts up however, only dropping cap_sys_admin results in an error. I've attached the debug output of # lxc-execute -o foo -l DEBUG -n foo -s lxc.cap.drop=sys_admin -- /bin/bash for reference. Release: 12.04.3 with HWE, Kernel 3.8.0-32-generic #47~precise1-Ubuntu SMP Wed Oct 2 16:19:35 UTC 2013 x86_64 LXC version: 1.0.0~alpha1-0ubuntu13~ubuntu12.04.1 -- 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/1253669 Title: unable to launch lxc application containers when dropping cap_sysadmin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1253669/+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 1253669] Re: unable to launch lxc application containers when dropping cap_sysadmin
** Description changed: SRU Justification 1. Impact: cannot lxc-execute a container without cap_sys_admin 2. Development fix: don't fail if lxc-init cannot mount /proc 3. Stable fix: same as development fix. 4. Test case: +sudo lxc-create -t ubuntu-cloud -n c1 +sudo lxc-start -n c1 +(log in) + sudo apt-get -y install --no-install-recommends lxc + sudo poweroff +sudo lxc-execcute -n c1 -s lxc.cap.drop=sys_admin /bin/bash 5. Regression potential: none Using the 0.8.0~rc1 lxc release, it was possible to start an application container with the lxc.cap.drop=sys_admin option (# lxc-execute -n foo -s lxc.cap.drop=sys_admin -- /bin/bash). Since the new 1.0.0~alpha1 release, this is not possible anymore; the application immediately crashes upon being called by lxc-init, thus killing the container. When any other capability (or combination of capabilities) is dropped, the container still starts up however, only dropping cap_sys_admin results in an error. I've attached the debug output of # lxc-execute -o foo -l DEBUG -n foo -s lxc.cap.drop=sys_admin -- /bin/bash for reference. Release: 12.04.3 with HWE, Kernel 3.8.0-32-generic #47~precise1-Ubuntu SMP Wed Oct 2 16:19:35 UTC 2013 x86_64 LXC version: 1.0.0~alpha1-0ubuntu13~ubuntu12.04.1 -- 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/1253669 Title: unable to launch lxc application containers when dropping cap_sysadmin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1253669/+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 1253669] Re: unable to launch lxc application containers when dropping cap_sysadmin
This bug was fixed in the package lxc - 1.0.0~alpha3-0ubuntu3 --- lxc (1.0.0~alpha3-0ubuntu3) trusty; urgency=low * d/p/0002-don-t-fail-lxc-init-if-we-couldn-t-mount-proc.patch: fix failure to run lxc-init when lxc.cap.drop=sys_admin. (LP: #1253669) -- Serge Hallyn serge.hal...@ubuntu.com Fri, 22 Nov 2013 15:57:59 -0600 ** Changed in: lxc (Ubuntu) Status: Fix Committed = 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/1253669 Title: unable to launch lxc application containers when dropping cap_sysadmin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1253669/+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 841672] Re: ssh-add does not always unlock ssh keys
This bug is present in Ubuntu 13.04. -- 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/841672 Title: ssh-add does not always unlock ssh keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/841672/+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
