[Bug 1288685] Re: dns-name key error race after bootstrap
This was resolved in 0.4 ** Changed in: juju-deployer Status: In Progress = Fix Released ** Changed in: juju-deployer Milestone: None = 0.4.0 ** Changed in: juju-deployer (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1288685 Title: dns-name key error race after bootstrap To manage notifications about this bug go to: https://bugs.launchpad.net/juju-deployer/+bug/1288685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1290847] Re: pyvenv fails due to mising ensurepip module
bug says fixed released, but this is still an issue on trusty. i don't see the value of virtualenvs without pip so that's not a viable workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1290847 Title: pyvenv fails due to mising ensurepip module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1290847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
just got a report of the same issue and resolution with 1.20.11 on orangebox maas. same s/br0/lxcbr0 fix for the container on machine 0. we tried again and got a slightly different issue on machine 2's container Forensenic status output - https://pastebin.canonical.com/119751/ failed container log output - https://pastebin.canonical.com/119742/ juju machine agent log - https://pastebin.canonical.com/119746/ cloudinit log - https://pastebin.canonical.com/119748/ ifconfig - https://pastebin.canonical.com/119752/ container config - https://pastebin.canonical.com/119753/ oddly on machine 0 the container had br0 for the bridge, its also failing on machine 2 but the lxc container appears to be targeted towards the correct bridge. -- 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/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+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 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
on machine 0 (orangebox kvm maas instance) the ifconfig output is https://pastebin.canonical.com/119756/ the lxc conf is https://pastebin.canonical.com/119757/ the container there also failed to start. -- 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/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+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 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
just got a report of the same issue and resolution with 1.20.11 on orangebox maas. same s/br0/lxcbr0 fix for the container on machine 0. we tried again and got a slightly different issue on machine 2's container Forensenic status output - https://pastebin.canonical.com/119751/ failed container log output - https://pastebin.canonical.com/119742/ juju machine agent log - https://pastebin.canonical.com/119746/ cloudinit log - https://pastebin.canonical.com/119748/ ifconfig - https://pastebin.canonical.com/119752/ container config - https://pastebin.canonical.com/119753/ oddly on machine 0 the container had br0 for the bridge, its also failing on machine 2 but the lxc container appears to be targeted towards the correct bridge. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
on machine 0 (orangebox kvm maas instance) the ifconfig output is https://pastebin.canonical.com/119756/ the lxc conf is https://pastebin.canonical.com/119757/ the container there also failed to start. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1355813] Re: LXC containers reset bridge MTU on start/restart
i've seen reference to you can't really set a bridge mtu, you have to set it for all the containers on the bridge, ie. bridges take the lowest mtu of their interfaces. so instead we have to set all the containers mtu. -- 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/1355813 Title: LXC containers reset bridge MTU on start/restart To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1355813/+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 1355813] Re: LXC containers reset bridge MTU on start/restart
i've seen reference to you can't really set a bridge mtu, you have to set it for all the containers on the bridge, ie. bridges take the lowest mtu of their interfaces. so instead we have to set all the containers mtu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1355813 Title: LXC containers reset bridge MTU on start/restart To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1355813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1374335] Re: FFe: Sync websocket-client 0.18.0-1 (universe) from Debian unstable (main), juju-deployer 0.4.2, python-jujuclient 0.18.4
there are no backwards incompatible changes from 0.16 to 0.18. there was one from 0.12 to 0.14 but 0.16 is already in debian and utopic. The fix from 0.16 to 0.18 is to support bypassing hostname verification (ssl.match_hostname) which is broken with ip addresses in python. ie. the full changelog from 0.16 to 0.18 is. v0.18.0 allow override of match_hostname usage on ssl (#105) v0.17.0 can't set timeout on a standing websocket connection (#102) fixed local variable 'error' referenced before assignment (#102, #98) per rdepends of python-websocket, i've manually verified this with the utopic version of docker-py its successfully passes its unit and functional tests with 0.18. The other rdepend is python-socketio-client which has bit-rotted unit tests and is broken independently and upstream for its core functionality with the socket.io 1.0 spec (see https://github.com/invisibleroads/socketIO-client/issues/52). That said it also has no issues with the 0.18 websocket client. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-quickstart in Ubuntu. https://bugs.launchpad.net/bugs/1374335 Title: FFe: Sync websocket-client 0.18.0-1 (universe) from Debian unstable (main), juju-deployer 0.4.2, python-jujuclient 0.18.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-deployer/+bug/1374335/+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 1374335] Re: FFe: Sync websocket-client 0.18.0-1 (universe) from Debian unstable (main), juju-deployer 0.4.2, python-jujuclient 0.18.4
there are no backwards incompatible changes from 0.16 to 0.18. there was one from 0.12 to 0.14 but 0.16 is already in debian and utopic. The fix from 0.16 to 0.18 is to support bypassing hostname verification (ssl.match_hostname) which is broken with ip addresses in python. ie. the full changelog from 0.16 to 0.18 is. v0.18.0 allow override of match_hostname usage on ssl (#105) v0.17.0 can't set timeout on a standing websocket connection (#102) fixed local variable 'error' referenced before assignment (#102, #98) per rdepends of python-websocket, i've manually verified this with the utopic version of docker-py its successfully passes its unit and functional tests with 0.18. The other rdepend is python-socketio-client which has bit-rotted unit tests and is broken independently and upstream for its core functionality with the socket.io 1.0 spec (see https://github.com/invisibleroads/socketIO-client/issues/52). That said it also has no issues with the 0.18 websocket client. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1374335 Title: FFe: Sync websocket-client 0.18.0-1 (universe) from Debian unstable (main), juju-deployer 0.4.2, python-jujuclient 0.18.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-deployer/+bug/1374335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1087183] Re: MaaS cloud-init configuration specifies 'manage_etc_hosts: localhost'
** Changed in: juju Status: Triaged = Won't Fix -- 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/1087183 Title: MaaS cloud-init configuration specifies 'manage_etc_hosts: localhost' To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1087183/+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 1087183] Re: MaaS cloud-init configuration specifies 'manage_etc_hosts: localhost'
** Changed in: juju Status: Triaged = Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1087183 Title: MaaS cloud-init configuration specifies 'manage_etc_hosts: localhost' To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1087183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368403] Re: juju-deployer traceback AttributeError: 'NoneType' object has no attribute 'get_stat'
bootstrap used to populate the jenv with state servers, i'll have deployer execute api-endpoints prior to attempting to connect. deployer does use the api, but it pre-dates most of it existing. although i implemented api-endpoints for core, the problem is api- endpoints is not sufficient if you want to securely connect (with cert verification) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1368403 Title: juju-deployer traceback AttributeError: 'NoneType' object has no attribute 'get_stat' To manage notifications about this bug go to: https://bugs.launchpad.net/juju-deployer/+bug/1368403/+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 1368403] Re: juju-deployer traceback AttributeError: 'NoneType' object has no attribute 'get_stat'
i've added a workaround and released 0.4.1 of juju-deployer to pypi. ** Changed in: juju-deployer Assignee: Jorge Niedbalski (niedbalski) = Kapil Thangavelu (hazmat) ** Changed in: juju-deployer Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1368403 Title: juju-deployer traceback AttributeError: 'NoneType' object has no attribute 'get_stat' To manage notifications about this bug go to: https://bugs.launchpad.net/juju-deployer/+bug/1368403/+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 1368403] Re: juju-deployer traceback AttributeError: 'NoneType' object has no attribute 'get_stat'
i'm curious which providers and versions of juju these issues are appear in, i'm seeing state-servers post bootstrap on manual and aws (1.21 trunk). ** Changed in: juju-deployer Importance: Undecided = Critical -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1368403 Title: juju-deployer traceback AttributeError: 'NoneType' object has no attribute 'get_stat' To manage notifications about this bug go to: https://bugs.launchpad.net/juju-deployer/+bug/1368403/+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 1368403] Re: juju-deployer traceback AttributeError: 'NoneType' object has no attribute 'get_stat'
in addition to the pypi release of 0.4.1, stable ppa will be updated tomorrow for those on packages, for now the workaround is to run juju api-endpoints or juju status prior to invoking deployer -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1368403 Title: juju-deployer traceback AttributeError: 'NoneType' object has no attribute 'get_stat' To manage notifications about this bug go to: https://bugs.launchpad.net/juju-deployer/+bug/1368403/+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 1323752] Re: unmet dependency: pkg_resources.DistributionNotFound: PyYAML==3.10
** Changed in: juju-deployer Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1323752 Title: unmet dependency: pkg_resources.DistributionNotFound: PyYAML==3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-deployer/+bug/1323752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318366] Re: jujud on state server panic misses transaction in queue
And the db dump (732k) of the juju db in mongo on mark's state server is at http://chinstrap.canonical.com/~kapil/bug-13183656-juju-db.dump.tbz2 -- 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/1318366 Title: jujud on state server panic misses transaction in queue To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1318366/+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 1318366] Re: jujud on state server panic misses transaction in queue
And the db dump (732k) of the juju db in mongo on mark's state server is at http://chinstrap.canonical.com/~kapil/bug-13183656-juju-db.dump.tbz2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318366 Title: jujud on state server panic misses transaction in queue To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1318366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1338768] Re: Please SRU 1.0.0~dfsg1-1 to trusty
the version we have in trusty is effectively a beta.. 1.0 is an upstream supported version and is pure bug fix over what we have in trusty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1338768 Title: Please SRU 1.0.0~dfsg1-1 to trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1338768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
using latest dailies images and/or hacking juju to not blindly issue apt-get update/upgrade is something i often to do safe a minute per unit (x100s). its also the only way to get kernel updates sans rebooting a machine post deploy. a daily should get us to the same place as the last release plus upgrades, however it does not get qa'd by the cloud images team. On Thu, May 29, 2014 at 11:33 AM, Serge Hallyn 1322...@bugs.launchpad.net wrote: So it looks like this should be reclassified against juju again? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- 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/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+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 1322302] Re: local provider is very slow to tranistion from agent-status: pending
using latest dailies images and/or hacking juju to not blindly issue apt-get update/upgrade is something i often to do safe a minute per unit (x100s). its also the only way to get kernel updates sans rebooting a machine post deploy. a daily should get us to the same place as the last release plus upgrades, however it does not get qa'd by the cloud images team. On Thu, May 29, 2014 at 11:33 AM, Serge Hallyn 1322...@bugs.launchpad.net wrote: So it looks like this should be reclassified against juju again? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1323752] Re: unmet dependency: pkg_resources.DistributionNotFound: PyYAML==3.10
noted and agreed ** Changed in: juju-deployer Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1323752 Title: unmet dependency: pkg_resources.DistributionNotFound: PyYAML==3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-deployer/+bug/1323752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1319555] Re: update out-dated ec2-api-tools for 12.04
nevermind, just noticed its already available On Tue, May 27, 2014 at 1:12 PM, Kapil Thangavelu kapil.thangav...@canonical.com wrote: shouldn't we be using/packaging awscli http://aws.amazon.com/cli/ which is a uniform/umbrella client to all the aws services On Tue, May 27, 2014 at 12:07 PM, Scott Moser smo...@ubuntu.com wrote: Marking this as fix-released in utopic. Ben got 1.6.13.0-0ubuntu1 uploaded, and I then uploaded 1.6.14.1-0ubuntu1 ** Changed in: ec2-api-tools (Ubuntu Utopic) Importance: High = Medium ** Changed in: ec2-api-tools (Ubuntu Utopic) Status: Invalid = Fix Released -- You received this bug notification because you are a member of Canonical Cloudware, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1319555 Title: update out-dated ec2-api-tools for 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-api-tools/+bug/1319555/+subscriptions -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ec2-api-tools in Ubuntu. https://bugs.launchpad.net/bugs/1319555 Title: update out-dated ec2-api-tools for 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-api-tools/+bug/1319555/+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 1319555] Re: update out-dated ec2-api-tools for 12.04
shouldn't we be using/packaging awscli http://aws.amazon.com/cli/ which is a uniform/umbrella client to all the aws services On Tue, May 27, 2014 at 12:07 PM, Scott Moser smo...@ubuntu.com wrote: Marking this as fix-released in utopic. Ben got 1.6.13.0-0ubuntu1 uploaded, and I then uploaded 1.6.14.1-0ubuntu1 ** Changed in: ec2-api-tools (Ubuntu Utopic) Importance: High = Medium ** Changed in: ec2-api-tools (Ubuntu Utopic) Status: Invalid = Fix Released -- You received this bug notification because you are a member of Canonical Cloudware, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1319555 Title: update out-dated ec2-api-tools for 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-api-tools/+bug/1319555/+subscriptions -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ec2-api-tools in Ubuntu. https://bugs.launchpad.net/bugs/1319555 Title: update out-dated ec2-api-tools for 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-api-tools/+bug/1319555/+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 1319555] Re: update out-dated ec2-api-tools for 12.04
nevermind, just noticed its already available On Tue, May 27, 2014 at 1:12 PM, Kapil Thangavelu kapil.thangav...@canonical.com wrote: shouldn't we be using/packaging awscli http://aws.amazon.com/cli/ which is a uniform/umbrella client to all the aws services On Tue, May 27, 2014 at 12:07 PM, Scott Moser smo...@ubuntu.com wrote: Marking this as fix-released in utopic. Ben got 1.6.13.0-0ubuntu1 uploaded, and I then uploaded 1.6.14.1-0ubuntu1 ** Changed in: ec2-api-tools (Ubuntu Utopic) Importance: High = Medium ** Changed in: ec2-api-tools (Ubuntu Utopic) Status: Invalid = Fix Released -- You received this bug notification because you are a member of Canonical Cloudware, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1319555 Title: update out-dated ec2-api-tools for 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-api-tools/+bug/1319555/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1319555 Title: update out-dated ec2-api-tools for 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-api-tools/+bug/1319555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1319555] Re: update out-dated ec2-api-tools for 12.04
shouldn't we be using/packaging awscli http://aws.amazon.com/cli/ which is a uniform/umbrella client to all the aws services On Tue, May 27, 2014 at 12:07 PM, Scott Moser smo...@ubuntu.com wrote: Marking this as fix-released in utopic. Ben got 1.6.13.0-0ubuntu1 uploaded, and I then uploaded 1.6.14.1-0ubuntu1 ** Changed in: ec2-api-tools (Ubuntu Utopic) Importance: High = Medium ** Changed in: ec2-api-tools (Ubuntu Utopic) Status: Invalid = Fix Released -- You received this bug notification because you are a member of Canonical Cloudware, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1319555 Title: update out-dated ec2-api-tools for 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-api-tools/+bug/1319555/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1319555 Title: update out-dated ec2-api-tools for 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-api-tools/+bug/1319555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313785] Re: Can't SSH with juju ssh command to EC2 instance.
** Also affects: juju-core Importance: Undecided Status: New -- 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/1313785 Title: Can't SSH with juju ssh command to EC2 instance. To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1313785/+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 1313785] Re: Can't SSH with juju ssh command to EC2 instance.
** Also affects: juju-core Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313785 Title: Can't SSH with juju ssh command to EC2 instance. To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1313785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284690] Re: all watcher api regression
** Changed in: juju-deployer Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-jujuclient in Ubuntu. https://bugs.launchpad.net/bugs/1284690 Title: all watcher api regression To manage notifications about this bug go to: https://bugs.launchpad.net/juju-deployer/+bug/1284690/+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 1284690] Re: all watcher api regression
** Changed in: juju-deployer Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1284690 Title: all watcher api regression To manage notifications about this bug go to: https://bugs.launchpad.net/juju-deployer/+bug/1284690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1288685] Re: dns-name key error race after bootstrap
** Changed in: juju-deployer Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1288685 Title: dns-name key error race after bootstrap To manage notifications about this bug go to: https://bugs.launchpad.net/juju-deployer/+bug/1288685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1288685] Re: dns-name key error race after bootstrap
** Changed in: juju-deployer Status: New = In Progress ** Changed in: juju-deployer Assignee: (unassigned) = Kapil Thangavelu (hazmat) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1288685 Title: dns-name key error race after bootstrap To manage notifications about this bug go to: https://bugs.launchpad.net/juju-deployer/+bug/1288685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1306298] [NEW] deployer fails to deploy bundle with subordinate (via gui)
Sorry I rather keep the API and hose the gui for now. Ie old version for truth on 0.3.4 On Friday, April 11, 2014, Launchpad Bug Tracker 1306...@bugs.launchpad.net wrote: This bug was fixed in the package juju-deployer - 0.3.6-0ubuntu2 --- juju-deployer (0.3.6-0ubuntu2) trusty; urgency=medium * d/p/fixup-suboridinates.patch: Fixup broken deployment of subordinates for the deployer CLI (LP: #1306298). -- James Page james.p...@ubuntu.com javascript:; Fri, 11 Apr 2014 16:36:01 +0100 ** Changed in: juju-deployer (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1306298 Title: deployer fails to deploy bundle with subordinate (via gui) To manage notifications about this bug go to: https://bugs.launchpad.net/juju-deployer/+bug/1306298/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1306298 Title: deployer fails to deploy bundle with subordinate (via gui) To manage notifications about this bug go to: https://bugs.launchpad.net/juju-deployer/+bug/1306298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284690] Re: all watcher api regression
uploaded jujuclient 0.17.5 to pypi to handle connection errors while stopping a watch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1284690 Title: all watcher api regression To manage notifications about this bug go to: https://bugs.launchpad.net/juju-deployer/+bug/1284690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284690] Re: all watcher api regression
last fix for reconnect had to be refactored, didn't work in the field, uploaded jujuclient-0.17.4 to pypi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1284690 Title: all watcher api regression To manage notifications about this bug go to: https://bugs.launchpad.net/juju-deployer/+bug/1284690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284690] Re: all watcher api regression
** Also affects: python-jujuclient Importance: Undecided Status: New ** Changed in: python-jujuclient Importance: Undecided = Critical ** Changed in: python-jujuclient Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1284690 Title: all watcher api regression To manage notifications about this bug go to: https://bugs.launchpad.net/juju-deployer/+bug/1284690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278491] Re: KeyError: 'admin-secret'
** Changed in: juju-deployer Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278491 Title: KeyError: 'admin-secret' To manage notifications about this bug go to: https://bugs.launchpad.net/juju-deployer/+bug/1278491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278491] Re: KeyError: 'admin-secret'
** Changed in: juju-deployer Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278491 Title: KeyError: 'admin-secret' To manage notifications about this bug go to: https://bugs.launchpad.net/juju-deployer/+bug/1278491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278491] Re: KeyError: 'admin-secret'
** Changed in: juju-deployer Status: New = Confirmed ** Changed in: juju-deployer Milestone: None = 0.3.3 ** Changed in: juju-deployer Status: Confirmed = In Progress ** Changed in: juju-deployer Assignee: (unassigned) = Kapil Thangavelu (hazmat) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278491 Title: KeyError: 'admin-secret' To manage notifications about this bug go to: https://bugs.launchpad.net/juju-deployer/+bug/1278491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278491] Re: KeyError: 'admin-secret'
** Changed in: juju-deployer Importance: Undecided = Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278491 Title: KeyError: 'admin-secret' To manage notifications about this bug go to: https://bugs.launchpad.net/juju-deployer/+bug/1278491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 955576] Re: 'local:' services not started on reboot
this bug is resolved in juju-core fwiw. On Fri, Dec 13, 2013 at 2:28 PM, Dimitri John Ledkov launch...@surgut.co.uk wrote: if lxc config is modified to autostart containers, those containers that are specified in /etc/lxc/auto will be auto started. This is from https://help.ubuntu.com/lts/serverguide/lxc.html -- You received this bug notification because you are subscribed to pyjuju. https://bugs.launchpad.net/bugs/955576 Title: 'local:' services not started on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/955576/+subscriptions -- 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/955576 Title: 'local:' services not started on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/955576/+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 955576] Re: 'local:' services not started on reboot
this bug is resolved in juju-core fwiw. On Fri, Dec 13, 2013 at 2:28 PM, Dimitri John Ledkov launch...@surgut.co.uk wrote: if lxc config is modified to autostart containers, those containers that are specified in /etc/lxc/auto will be auto started. This is from https://help.ubuntu.com/lts/serverguide/lxc.html -- You received this bug notification because you are subscribed to pyjuju. https://bugs.launchpad.net/bugs/955576 Title: 'local:' services not started on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/955576/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/955576 Title: 'local:' services not started on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/955576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1129720] Re: juju instances not including the default security group
not quite the same, but juju environments also have a default group that this these rules can be applied to once per env. On Tue, Nov 19, 2013 at 10:43 PM, Haw Loeung 1129...@bugs.launchpad.netwrote: ** Also affects: juju-core Importance: Undecided Status: New ** Also affects: juju-core (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are subscribed to pyjuju. https://bugs.launchpad.net/bugs/1129720 Title: juju instances not including the default security group To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1129720/+subscriptions -- 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/1129720 Title: juju instances not including the default security group To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1129720/+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 1129720] Re: juju instances not including the default security group
not quite the same, but juju environments also have a default group that this these rules can be applied to once per env. On Tue, Nov 19, 2013 at 10:43 PM, Haw Loeung 1129...@bugs.launchpad.netwrote: ** Also affects: juju-core Importance: Undecided Status: New ** Also affects: juju-core (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are subscribed to pyjuju. https://bugs.launchpad.net/bugs/1129720 Title: juju instances not including the default security group To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1129720/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1129720 Title: juju instances not including the default security group To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1129720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1061787] Re: Dual Monitor Lock Screen Dialog Hidden
*** This bug is a duplicate of bug 998735 *** https://bugs.launchpad.net/bugs/998735 I get this on an intel graphic drivers as well, And even worse, if you try to enter your password twice, it will go to whatever the app in the foreground is. you can't see anything.. so there's no feedback if it comes back or not.. and sometimes it does when the screensaver goes away, sometimes not. i've revealed my login password to irc several times this way over the years. ouch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1061787 Title: Dual Monitor Lock Screen Dialog Hidden To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/1061787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242237] Re: Mongodb server ignores --smallfiles if other paramethers are set in the command line
** Also affects: juju-core Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1242237 Title: Mongodb server ignores --smallfiles if other paramethers are set in the command line To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1242237/+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 1242237] Re: Mongodb server ignores --smallfiles if other paramethers are set in the command line
** Also affects: juju-core Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242237 Title: Mongodb server ignores --smallfiles if other paramethers are set in the command line To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1242237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070519] Re: zookeeper: WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn$Factory@247] - Too many connections from /127.0.0.1 - max is 10
landed in 0.6 ppa (precise default) ** Changed in: juju (Ubuntu) Status: In Progress = 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/1070519 Title: zookeeper: WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn$Factory@247] - Too many connections from /127.0.0.1 - max is 10 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1070519/+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 1070519] Re: zookeeper: WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn$Factory@247] - Too many connections from /127.0.0.1 - max is 10
landed in 0.6 ppa (precise default) ** Changed in: juju (Ubuntu) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070519 Title: zookeeper: WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn$Factory@247] - Too many connections from /127.0.0.1 - max is 10 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1070519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1214172] Re: juju/MAAS Tag constraints do not work in Precise
what's the output of $ apt-cache policy juju on the bootstrap node. i assume this is precise with juju-origin:ppa ? -- 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/1214172 Title: juju/MAAS Tag constraints do not work in Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1214172/+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 1214172] Re: juju/MAAS Tag constraints do not work in Precise
the behavior of juju-origin: ppa varies by client version and installation mechanism (a questionable choice that's embedded in the packaging), could confirm the version of juju on the bootstrap server per previous. -- 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/1214172 Title: juju/MAAS Tag constraints do not work in Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1214172/+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 1070519] Re: zookeeper: WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn$Factory@247] - Too many connections from /127.0.0.1 - max is 10
its destined for the ppa (waiting on builders atm), its already tested and landed on the 0.6 branch (juju-origin: lp:juju/0.6) -- 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/1070519 Title: zookeeper: WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn$Factory@247] - Too many connections from /127.0.0.1 - max is 10 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1070519/+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 1214172] Re: juju/MAAS Tag constraints do not work in Precise
what's the output of $ apt-cache policy juju on the bootstrap node. i assume this is precise with juju-origin:ppa ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1214172 Title: juju/MAAS Tag constraints do not work in Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1214172/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1214172] Re: juju/MAAS Tag constraints do not work in Precise
the behavior of juju-origin: ppa varies by client version and installation mechanism (a questionable choice that's embedded in the packaging), could confirm the version of juju on the bootstrap server per previous. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1214172 Title: juju/MAAS Tag constraints do not work in Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1214172/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070519] Re: zookeeper: WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn$Factory@247] - Too many connections from /127.0.0.1 - max is 10
its destined for the ppa (waiting on builders atm), its already tested and landed on the 0.6 branch (juju-origin: lp:juju/0.6) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070519 Title: zookeeper: WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn$Factory@247] - Too many connections from /127.0.0.1 - max is 10 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1070519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070519] Re: zookeeper: WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn$Factory@247] - Too many connections from /127.0.0.1 - max is 10
** Changed in: juju (Ubuntu) Assignee: (unassigned) = Kapil Thangavelu (hazmat) ** Changed in: juju (Ubuntu) Status: Confirmed = In Progress -- 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/1070519 Title: zookeeper: WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn$Factory@247] - Too many connections from /127.0.0.1 - max is 10 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1070519/+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 1070519] Re: zookeeper: WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn$Factory@247] - Too many connections from /127.0.0.1 - max is 10
** Changed in: juju (Ubuntu) Assignee: (unassigned) = Kapil Thangavelu (hazmat) ** Changed in: juju (Ubuntu) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070519 Title: zookeeper: WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn$Factory@247] - Too many connections from /127.0.0.1 - max is 10 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1070519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070519] Re: zookeeper: WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn$Factory@247] - Too many connections from /127.0.0.1 - max is 10
The solution requires modifying the zookeeper config, its resolved in trunk, but not in the 0.6 ppa. It can manually resolved via echo maxClientCnxns=500 /etc/zookeeper/conf/zoo.cfg on the bootstrap node. -- 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/1070519 Title: zookeeper: WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn$Factory@247] - Too many connections from /127.0.0.1 - max is 10 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1070519/+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 1070519] Re: zookeeper: WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn$Factory@247] - Too many connections from /127.0.0.1 - max is 10
the maxclientcnxns adjustment also needs a restart of zookeeper.. -- 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/1070519 Title: zookeeper: WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn$Factory@247] - Too many connections from /127.0.0.1 - max is 10 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1070519/+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 1070519] Re: zookeeper: WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn$Factory@247] - Too many connections from /127.0.0.1 - max is 10
The solution requires modifying the zookeeper config, its resolved in trunk, but not in the 0.6 ppa. It can manually resolved via echo maxClientCnxns=500 /etc/zookeeper/conf/zoo.cfg on the bootstrap node. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070519 Title: zookeeper: WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn$Factory@247] - Too many connections from /127.0.0.1 - max is 10 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1070519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070519] Re: zookeeper: WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn$Factory@247] - Too many connections from /127.0.0.1 - max is 10
the maxclientcnxns adjustment also needs a restart of zookeeper.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070519 Title: zookeeper: WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn$Factory@247] - Too many connections from /127.0.0.1 - max is 10 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1070519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1130809] Re: lxc scripts break when user has PYTHONPATH set
** Changed in: juju Status: Incomplete = Fix Committed ** Changed in: juju Milestone: None = 0.7.1 ** Changed in: juju Assignee: (unassigned) = Kapil Thangavelu (hazmat) -- 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/1130809 Title: lxc scripts break when user has PYTHONPATH set To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1130809/+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 1130809] Re: lxc scripts break when user has PYTHONPATH set
** Changed in: juju Status: Incomplete = Fix Committed ** Changed in: juju Milestone: None = 0.7.1 ** Changed in: juju Assignee: (unassigned) = Kapil Thangavelu (hazmat) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1130809 Title: lxc scripts break when user has PYTHONPATH set To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1130809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103881] Re: cloud-final is never executed if upstart is upgraded during initialization of the image
i see the issue even without an upstart upgrade.. my upgrade list is. note cloud-init is part of the list. apparmor apport apt apt-transport-https apt-utils base-files cloud-init curl gcc-4.7-base gir1.2-gudev-1.0 grub-common grub-legacy-ec2 grub-pc grub-pc-bin grub2-common kmod language-selector-common libapt-inst1.5 libapt-pkg4.12 libc-bin libc6 libcurl3 libcurl3-gnutls libgcc1 libglib2.0-0 libgudev-1.0-0 libisccc90 libkmod2 libpci3 libpython-stdlib libpython2.7 libpython2.7-minimal libpython2.7-stdlib libpython3-stdlib libpython3.3-minimal libpython3.3-stdlib libstdc++6 libudev1 login module-init-tools multiarch-support ntpdate passwd pciutils perl perl-base perl-modules python python-gi python-minimal python-pycurl python-twisted-bin python-twisted-core python2.7 python2.7-minimal python3 python3-apport python3-distupgrade python3-gi python3-minimal python3-problem-report python3-update-manager python3.3 python3.3-minimal rsyslog tar ubuntu-minimal ubuntu-release-upgrader-core ubuntu-standard udev update-manager-core update-notifier-common -- 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/1103881 Title: cloud-final is never executed if upstart is upgraded during initialization of the image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1103881/+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 1103881] Re: cloud-final is never executed if upstart is upgraded during initialization of the image
i see the issue even without an upstart upgrade.. my upgrade list is. note cloud-init is part of the list. apparmor apport apt apt-transport-https apt-utils base-files cloud-init curl gcc-4.7-base gir1.2-gudev-1.0 grub-common grub-legacy-ec2 grub-pc grub-pc-bin grub2-common kmod language-selector-common libapt-inst1.5 libapt-pkg4.12 libc-bin libc6 libcurl3 libcurl3-gnutls libgcc1 libglib2.0-0 libgudev-1.0-0 libisccc90 libkmod2 libpci3 libpython-stdlib libpython2.7 libpython2.7-minimal libpython2.7-stdlib libpython3-stdlib libpython3.3-minimal libpython3.3-stdlib libstdc++6 libudev1 login module-init-tools multiarch-support ntpdate passwd pciutils perl perl-base perl-modules python python-gi python-minimal python-pycurl python-twisted-bin python-twisted-core python2.7 python2.7-minimal python3 python3-apport python3-distupgrade python3-gi python3-minimal python3-problem-report python3-update-manager python3.3 python3.3-minimal rsyslog tar ubuntu-minimal ubuntu-release-upgrader-core ubuntu-standard udev update-manager-core update-notifier-common -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103881 Title: cloud-final is never executed if upstart is upgraded during initialization of the image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1103881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 813773] Re: Juju should have security rules/acls for every path in zk
** Changed in: juju Milestone: 0.7 = 0.8 -- 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/813773 Title: Juju should have security rules/acls for every path in zk To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/813773/+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 955576] Re: 'local:' services not started on reboot
** Changed in: juju Milestone: None = 0.8 -- 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/955576 Title: 'local:' services not started on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/955576/+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 966577] Re: add explicit egress 'owner' rule on non-bootstrapping nodes to require root access to zookeeper
** Changed in: juju Milestone: 0.7 = 0.8 -- 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/966577 Title: add explicit egress 'owner' rule on non-bootstrapping nodes to require root access to zookeeper To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/966577/+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 813773] Re: Juju should have security rules/acls for every path in zk
** Changed in: juju Milestone: 0.7 = 0.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/813773 Title: Juju should have security rules/acls for every path in zk To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/813773/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1054096] Re: Openstack folsom compatibility (Rackspace Cloud Specifically)
** Changed in: juju Assignee: Martin Packman (gz) = (unassigned) ** Summary changed: - Openstack folsom compatibility (Rackspace Cloud Specifically) + Openstack rackspace compatibility ** Changed in: juju Milestone: 0.7 = 0.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1054096 Title: Openstack rackspace compatibility To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1054096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 955576] Re: 'local:' services not started on reboot
** Changed in: juju Milestone: None = 0.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/955576 Title: 'local:' services not started on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/955576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 966577] Re: add explicit egress 'owner' rule on non-bootstrapping nodes to require root access to zookeeper
** Changed in: juju Milestone: 0.7 = 0.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/966577 Title: add explicit egress 'owner' rule on non-bootstrapping nodes to require root access to zookeeper To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/966577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1118815] Re: Remove python-oauth from the archive
** Changed in: juju Importance: Undecided = Low ** Changed in: juju Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1118815 Title: Remove python-oauth from the archive To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1118815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1111883] Re: Peer relation listed in relation-ids, but not queryable using relation-list
** Changed in: juju Status: In Progress = Fix Released ** Changed in: juju (Ubuntu) Status: New = 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/883 Title: Peer relation listed in relation-ids, but not queryable using relation-list To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/883/+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 1111883] Re: Peer relation listed in relation-ids, but not queryable using relation-list
** Changed in: juju Status: In Progress = Fix Released ** Changed in: juju (Ubuntu) Status: New = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883 Title: Peer relation listed in relation-ids, but not queryable using relation-list To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1068566] Re: Juju 0.6 incompatible with MAAS in precise
** Changed in: juju 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/1068566 Title: Juju 0.6 incompatible with MAAS in precise To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1068566/+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 920454] Re: juju bootstrap hangs for local environment under precise on vmware
in addition to being fixed in quantal we're also no longer using libvirt networking.. marking resolved. ** Changed in: juju Status: Triaged = Fix Released ** Changed in: juju Milestone: None = 0.6.1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/920454 Title: juju bootstrap hangs for local environment under precise on vmware To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/920454/+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 1078217] Re: zookeeper connection is not using exponential backoff
** Also affects: txzookeeper Importance: Undecided Status: New -- 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/1078217 Title: zookeeper connection is not using exponential backoff To manage notifications about this bug go to: https://bugs.launchpad.net/txzookeeper/+bug/1078217/+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 1111883] Re: Peer relation listed in relation-ids, but not queryable using relation-list
** Also affects: juju Importance: Undecided Status: New ** Changed in: juju Status: New = In Progress ** Changed in: juju Importance: Undecided = High ** Changed in: juju Assignee: (unassigned) = Kapil Thangavelu (hazmat) ** Changed in: juju Milestone: None = 0.7 ** Branch linked: lp:~hazmat/juju/sane-relation-ids -- 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/883 Title: Peer relation listed in relation-ids, but not queryable using relation-list To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/883/+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 1070639] Re: juju status trigger errors within my node's logs
so zookeeper logs this exception for normal client operations, this isn't a bug. ** Summary changed: - juju status trigger errors within my node's logs + juju status trigger errors within my zk logs -- 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/1070639 Title: juju status trigger errors within my zk logs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1070639/+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 1098634] Re: incorrect bzr invocation on certain charm gets
** Also affects: charm-tools Importance: Undecided Status: New -- 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/1098634 Title: incorrect bzr invocation on certain charm gets To manage notifications about this bug go to: https://bugs.launchpad.net/charm-tools/+bug/1098634/+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 1068566] Re: Juju 0.6 incompatible with MAAS in precise
** Changed in: juju Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1068566 Title: Juju 0.6 incompatible with MAAS in precise To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1068566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 920454] Re: juju bootstrap hangs for local environment under precise on vmware
in addition to being fixed in quantal we're also no longer using libvirt networking.. marking resolved. ** Changed in: juju Status: Triaged = Fix Released ** Changed in: juju Milestone: None = 0.6.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/920454 Title: juju bootstrap hangs for local environment under precise on vmware To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/920454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1078217] Re: zookeeper connection is not using exponential backoff
** Also affects: txzookeeper Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1078217 Title: zookeeper connection is not using exponential backoff To manage notifications about this bug go to: https://bugs.launchpad.net/txzookeeper/+bug/1078217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1111883] Re: Peer relation listed in relation-ids, but not queryable using relation-list
** Also affects: juju Importance: Undecided Status: New ** Changed in: juju Status: New = In Progress ** Changed in: juju Importance: Undecided = High ** Changed in: juju Assignee: (unassigned) = Kapil Thangavelu (hazmat) ** Changed in: juju Milestone: None = 0.7 ** Branch linked: lp:~hazmat/juju/sane-relation-ids -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883 Title: Peer relation listed in relation-ids, but not queryable using relation-list To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070639] Re: juju status trigger errors within my node's logs
so zookeeper logs this exception for normal client operations, this isn't a bug. ** Summary changed: - juju status trigger errors within my node's logs + juju status trigger errors within my zk logs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070639 Title: juju status trigger errors within my zk logs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1070639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1098634] Re: incorrect bzr invocation on certain charm gets
** Also affects: charm-tools Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1098634 Title: incorrect bzr invocation on certain charm gets To manage notifications about this bug go to: https://bugs.launchpad.net/charm-tools/+bug/1098634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1054096] Re: Openstack folsom compatibility
Everything ;-) So we need to maintain compatibility with diablo/hpcloud and essex. The core of the changes are nova-volume and nova-network split out into separate services (cinder quantum). We'll need to do some more magic around svc catalog introspection and dispatch of capabilities handling to appropriate endpoint. -k On Thu, Sep 27, 2012 at 12:22 PM, Martin Packman martin.pack...@canonical.com wrote: So, what specifically is broken so I can update the api usage? -- 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/1054096 Title: Openstack folsom compatibility To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1054096/+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 1054096] Re: Openstack folsom compatibility
This is also what rackspace public cloud v2 offering is on. Their service catalog is a bit complicated because it also has multiple nova endpoint versions advertised in it (relating to the fact they really have more than one implementation to choose from). -k On Tue, Oct 2, 2012 at 12:22 PM, Kapil Thangavelu kapil.thangav...@canonical.com wrote: Everything ;-) So we need to maintain compatibility with diablo/hpcloud and essex. The core of the changes are nova-volume and nova-network split out into separate services (cinder quantum). We'll need to do some more magic around svc catalog introspection and dispatch of capabilities handling to appropriate endpoint. -k On Thu, Sep 27, 2012 at 12:22 PM, Martin Packman martin.pack...@canonical.com wrote: So, what specifically is broken so I can update the api usage? -- 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/1054096 Title: Openstack folsom compatibility To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1054096/+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 1054096] Re: Openstack folsom compatibility
Everything ;-) So we need to maintain compatibility with diablo/hpcloud and essex. The core of the changes are nova-volume and nova-network split out into separate services (cinder quantum). We'll need to do some more magic around svc catalog introspection and dispatch of capabilities handling to appropriate endpoint. -k On Thu, Sep 27, 2012 at 12:22 PM, Martin Packman martin.pack...@canonical.com wrote: So, what specifically is broken so I can update the api usage? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1054096 Title: Openstack folsom compatibility To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1054096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1054096] Re: Openstack folsom compatibility
This is also what rackspace public cloud v2 offering is on. Their service catalog is a bit complicated because it also has multiple nova endpoint versions advertised in it (relating to the fact they really have more than one implementation to choose from). -k On Tue, Oct 2, 2012 at 12:22 PM, Kapil Thangavelu kapil.thangav...@canonical.com wrote: Everything ;-) So we need to maintain compatibility with diablo/hpcloud and essex. The core of the changes are nova-volume and nova-network split out into separate services (cinder quantum). We'll need to do some more magic around svc catalog introspection and dispatch of capabilities handling to appropriate endpoint. -k On Thu, Sep 27, 2012 at 12:22 PM, Martin Packman martin.pack...@canonical.com wrote: So, what specifically is broken so I can update the api usage? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1054096 Title: Openstack folsom compatibility To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1054096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1048533] Re: Backport OpenStack provider to 0.5 series
Default instance type is obsolete in config, proper constraints supports exist in openstack provider Sent from my iPad On Sep 27, 2012, at 3:11 PM, Clint Byrum cl...@fewbar.com wrote: ** Description changed: + == SRU Information == + + Note that this is not a bug fix bug a backported API enablement fix. + Without this change, HPCloud and others cannot be used with juju in + precise. + + [Test Case] + 1. Obtain credentials for an OpenStack cloud (HPCloud or a private instance of OpenStack) + 2. Setup your credentials in ~/.juju/environments.yaml - Here is a redacted sample for hpcloud: + + hpcloud: + juju-origin: proposed + access-key: + secret-key: + project-id: yourem...@yourdomain.foo-tenant1 + admin-secret: + control-bucket: juju- + default-image-id: 8419 + default-instance-type: standard.small + default-series: precise + region: az-1.region-a.geo-1 + nova-uri: https://region-a.geo-1.identity.hpcloudsvc.com:35357/v2.0/ + auth-url: https://region-a.geo-1.identity.hpcloudsvc.com:35357/v2.0/ + auth-mode: userpass + username: yourem...@yourdomain.foo + password: + project-name: yourem...@yourdomain.com-tenant1 + type: openstack + + 3. deploy mysql + + juju bootstrap -e hpcloud + juju deploy mysql -e hpcloud + + 4. Verify it works + + juju ssh -e hpcloud mysql/0 'sudo mysql -uroot -p`cat + /var/lib/juju/mysql.passwd`' + + [Regression Potential] + This is entirely new code, so the risk of regression is very low. One issue may be that entries of type: openstack added to environments.yaml will cause errors on earlier versions of juju, but these can be easily commented out. + + == + The OpenStack provider is fairly isolated from the rest of the code base in Juju, and enables access to additional cloud providers (Namely, HP). -- You received this bug notification because you are subscribed to juju. https://bugs.launchpad.net/bugs/1048533 Title: Backport OpenStack provider to 0.5 series To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1048533/+subscriptions -- 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/1048533 Title: Backport OpenStack provider to 0.5 series To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1048533/+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 1048533] Re: Backport OpenStack provider to 0.5 series
Default instance type is obsolete in config, proper constraints supports exist in openstack provider Sent from my iPad On Sep 27, 2012, at 3:11 PM, Clint Byrum cl...@fewbar.com wrote: ** Description changed: + == SRU Information == + + Note that this is not a bug fix bug a backported API enablement fix. + Without this change, HPCloud and others cannot be used with juju in + precise. + + [Test Case] + 1. Obtain credentials for an OpenStack cloud (HPCloud or a private instance of OpenStack) + 2. Setup your credentials in ~/.juju/environments.yaml - Here is a redacted sample for hpcloud: + + hpcloud: + juju-origin: proposed + access-key: + secret-key: + project-id: yourem...@yourdomain.foo-tenant1 + admin-secret: + control-bucket: juju- + default-image-id: 8419 + default-instance-type: standard.small + default-series: precise + region: az-1.region-a.geo-1 + nova-uri: https://region-a.geo-1.identity.hpcloudsvc.com:35357/v2.0/ + auth-url: https://region-a.geo-1.identity.hpcloudsvc.com:35357/v2.0/ + auth-mode: userpass + username: yourem...@yourdomain.foo + password: + project-name: yourem...@yourdomain.com-tenant1 + type: openstack + + 3. deploy mysql + + juju bootstrap -e hpcloud + juju deploy mysql -e hpcloud + + 4. Verify it works + + juju ssh -e hpcloud mysql/0 'sudo mysql -uroot -p`cat + /var/lib/juju/mysql.passwd`' + + [Regression Potential] + This is entirely new code, so the risk of regression is very low. One issue may be that entries of type: openstack added to environments.yaml will cause errors on earlier versions of juju, but these can be easily commented out. + + == + The OpenStack provider is fairly isolated from the rest of the code base in Juju, and enables access to additional cloud providers (Namely, HP). -- You received this bug notification because you are subscribed to juju. https://bugs.launchpad.net/bugs/1048533 Title: Backport OpenStack provider to 0.5 series To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1048533/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1048533 Title: Backport OpenStack provider to 0.5 series To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1048533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 930430] Re: lxc-ls requires root access after deploying an LXC instance
I've just noticed this with some of the unit tests, afaik this is some change in lxc behavior. $ lxc-ls kapil-dev-0-template kapil-dev-wordpress-0 monitoring /usr/bin/lxc-ls: line 35: cd: /sys/fs/cgroup/cpuset///lxc: Permission denied ls: cannot access kapil-dev-wordpress-0: No such file or directory it only happens for trying to access the running containers. -k On Thu, Sep 20, 2012 at 1:31 AM, Clint Byrum cl...@fewbar.com wrote: ** Also affects: juju Importance: Undecided Status: New ** Changed in: juju Status: New = Triaged ** Changed in: juju Importance: Undecided = High ** Changed in: juju Milestone: None = 0.6 -- You received this bug notification because you are subscribed to juju. https://bugs.launchpad.net/bugs/930430 Title: lxc-ls requires root access after deploying an LXC instance To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/930430/+subscriptions -- 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/930430 Title: lxc-ls requires root access after deploying an LXC instance To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/930430/+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 930430] Re: lxc-ls requires root access after deploying an LXC instance
I've just noticed this with some of the unit tests, afaik this is some change in lxc behavior. $ lxc-ls kapil-dev-0-template kapil-dev-wordpress-0 monitoring /usr/bin/lxc-ls: line 35: cd: /sys/fs/cgroup/cpuset///lxc: Permission denied ls: cannot access kapil-dev-wordpress-0: No such file or directory it only happens for trying to access the running containers. -k On Thu, Sep 20, 2012 at 1:31 AM, Clint Byrum cl...@fewbar.com wrote: ** Also affects: juju Importance: Undecided Status: New ** Changed in: juju Status: New = Triaged ** Changed in: juju Importance: Undecided = High ** Changed in: juju Milestone: None = 0.6 -- You received this bug notification because you are subscribed to juju. https://bugs.launchpad.net/bugs/930430 Title: lxc-ls requires root access after deploying an LXC instance To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/930430/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/930430 Title: lxc-ls requires root access after deploying an LXC instance To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/930430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1048864] Re: Latest python in quantal breaks juju
** Summary changed: - Latest python in quantal breaks juju test suite + Latest python in quantal breaks 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/1048864 Title: Latest python in quantal breaks juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1048864/+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 1048864] Re: Latest python in quantal breaks juju
** Summary changed: - Latest python in quantal breaks juju test suite + Latest python in quantal breaks juju -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1048864 Title: Latest python in quantal breaks juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1048864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Blueprint servercloud-q-juju-charm-best-practices] Juju Charm Best practices
Blueprint changed by Kapil Thangavelu: Work items changed: Work items: [jorge] Pick better example charms, flagbearer charms.: TODO [jorge] Choose a single place for presenting flagbearer charms (charm browser?): TODO [jorge] Move rules and charm best practices into juju/docs.: DONE [jorge] Add Maintainer field information to documentation. (thanks clint!): DONE [jorge] Reach out to maintainers to get their maintainer field filled out.: INPROGRESS [jorge] Add docs work items to patch pilot!: DONE [jorge] pull file bug or join the doc team from other projects: TODO [jorge] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. You should expect this to download 300 megs, etc. Here's a table of look here troubleshooting your LXC thing: DONE [imbrandon] Reach out to maintainers to get their maintainer filled out.: TODO [imbrandon] Put Doc instructions in the docs: http://askubuntu.com/q/52063 : TODO [mark-mims] (and individual maintainers!) clean up existing charms wrt best practices: TODO [clint-fewbar] Comment and add links to docs in 'charm create' templates: TODO [clint-fewbar] juju in Debian! NOW!: DONE [clint-fewbar] determine most likely maintainers based on bzr logs: DONE [clint-fewbar] fix doc repos wrt (trunk, go, docs): DONE [marcoceppi] tag:juju review on AU and SE network: TODO - [hazmat] incorporate output of charm proof into charm browser: TODO - [hazmat] clear out trunk docs for juju: TODO + [hazmat] incorporate output of charm proof into charm browser: DONE + [hazmat] clear out trunk docs for juju: DONE [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. You should expect this to download 300 megs, etc. Here's a table of look here troubleshooting your LXC thing.: TODO [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. You should expect this to download 300 megs, etc. Here's a table of look here troubleshooting your LXC thing.: TODO [hazmat] make juju report on initial lxc image downloads ?: TODO [hazmat] make juju lxc use lxc networking instead of libvirt networking ?: TODO -- Juju Charm Best practices https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-best-practices -- 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/scp commands cause spurious key errors, should use a different known_hosts file
** Changed in: juju Assignee: Jim Baker (jimbaker) = (unassigned) ** Changed in: juju Status: In Progress = Confirmed -- 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
