[Bug 1369792] Re: Python yaml missing from mongodb install on precise and trusty
Moving to proper project, this effects juju not the ubuntu package. ** Package changed: mongodb (Ubuntu) => mongodb (Juju Charms Collection) ** Changed in: mongodb (Juju Charms Collection) Status: New => Confirmed ** Changed in: mongodb (Juju Charms Collection) Importance: Undecided => High ** Changed in: mongodb (Juju Charms Collection) Assignee: (unassigned) => Charles Butler (lazypower) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1369792 Title: Python yaml missing from mongodb install on precise and trusty To manage notifications about this bug go to: https://bugs.launchpad.net/charms/+source/mongodb/+bug/1369792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296384] Re: LXC apparmor profile broken w/recent trusty update
*** This bug is a duplicate of bug 1296459 *** https://bugs.launchpad.net/bugs/1296459 I've got the same behavior with juju local provider - apparmor is blockign LXC container creation [ 1945.253827] type=1400 audit(1400078670.232:91): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc- container-default" name="/run/rpc_pipefs/" pid=23261 comm="mount" fstype="rpc_pipefs" srcname="rpc_pipefs" flags="rw" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296384 Title: LXC apparmor profile broken w/recent trusty update To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1296384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 744223] Re: memslap / memcslap is not present, although it is advertised in the package libmemcached-tools
This is still an issue present in 13.10 ii libmemcached-tools1.0.8-1ubuntu1 amd64Commandline tools for talking to memcached via libmemcached charles@Bushido:~/cabs/precise/memslap$ type memslap bash: type: memslap: not found -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/744223 Title: memslap / memcslap is not present, although it is advertised in the package libmemcached-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmemcached/+bug/744223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 744223] Re: memslap / memcslap is not present, although it is advertised in the package libmemcached-tools
Disregard, the command was memcslap. I clearly didn't read the helpful output: $ memslap No command 'memslap' found, did you mean: Command 'memcslap' from package 'libmemcached-tools' (main) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/744223 Title: memslap / memcslap is not present, although it is advertised in the package libmemcached-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmemcached/+bug/744223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1329429] Re: local bootstrap fails
The issue turned out to be root owned ~/.juju/environments from what I observed. This can be resolved by removing that directory and letting juju re-create the directory to warehouse the .jenv's with the proper permissions on bootstrap. Can you give that a Go nuclearbob and let me know if the issue goes away? Please note, you no longer need to use sudo to bootstrap *any* environment. If juju requires sudo rights, it will prompt you for an administrative password. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1329429 Title: local bootstrap fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1329429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1407841] [NEW] docker.io package fails install if docker group is pre-existing
Public bug reported: When installing the docker.io package, it fails during installation with a message akin to the following: stderr: addgroup: The group `docker' already exists and is not a system group. Exiting. dpkg: error processing package docker.io (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: docker.io E: Sub-process /usr/bin/dpkg returned an error code (1) This was originally discovered during charm development where a user can switch from the canonical docker package to the docker maintained package 'lxc-docker'. With the upstream package, they are not maintaining a docker-group in the charm, and allows for installation regardless of the presence of the group. While the docker.io package will halt installation in a panic if it exists - regardless if its a system group or not. Just the presence alone appears to be the key factor in the failure. I don't think this behavior is correct - as a user may have created a docker group themselves, and expect to install the docker.io package from the repository after removing the latest - due to a bug or any number of reasons. I'm linking the commit to the charm and the user stack trace for additional validation/investigation if required: https://github.com/chuckbutler/docker- charm/commit/59946a7bd6bfa3cc050de3b27e62d3207c71be47 https://gist.github.com/slatunje/735e1e5132de02a3ad1d ** Affects: docker.io (Ubuntu) Importance: Undecided Status: New ** Tags: papercut -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1407841 Title: docker.io package fails install if docker group is pre-existing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1407841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1407841] Re: docker.io package fails install if docker group is pre-existing
I suppose that's a fair assesment. We took this route to clean up the charm code as well - just removing the group, but having a bug here marked as opinion shows the due dilligence :) Thanks for the rapid response Paul! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1407841 Title: docker.io package fails install if docker group is pre-existing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1407841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1235754] Re: quassel-* entry missing from indicator plugin (envelope), and tray icon doesn't work.
Important to note, this is still an issue in 13.10 and 14.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1235754 Title: quassel-* entry missing from indicator plugin (envelope), and tray icon doesn't work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1235754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
