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
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
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
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
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
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
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
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,
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
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
** 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:
** 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
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
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
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
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
** 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:
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.
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
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
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
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
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:
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
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
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
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
** 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.
** 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
** 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
** 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
** 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
** 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
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;
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
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
** 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,
** 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
** 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
** 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
** 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:
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
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
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:
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:
*** 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
** 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
** 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
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:
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
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:
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
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
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
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,
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:
** 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
** 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
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,
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
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
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
** 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
** 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
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
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
** 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
** 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
** 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
** 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
** 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
** 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:
** 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
** 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
** 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
** 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
** 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
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
** 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
** 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
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
** 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
** 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
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,
** 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
** 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
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
** 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
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
, 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
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
, 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
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
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
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
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
** 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
** 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
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
** 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
1 - 100 of 189 matches
Mail list logo
