Re: [Canonical-juju-qa] Cursed (final): #1479 gitbranch:master:github.com/juju/juju ead2e2d6 (functional-ha-recovery, hp-upgrade-precise-amd64)

2014-06-14 Thread John Meinel
So after poking around and trying to enable debugging, I did come across this line: 2014-06-14 10:04:08 INFO juju.mongo session.go:2191 queryError: &mgo.queryError{Err:"not authorized for query on local.system.replset", ErrMsg:"", Assertion:"", Code:16550, AssertionCode:0, LastError:(*mgo.LastError

Re: bootstrap && status still down?

2014-06-14 Thread Wayne Witzel
Hopefully it will land Monday :) On Sat, Jun 14, 2014 at 4:40 AM, John Meinel wrote: > Ah, ok. I remembered reviewing that and wanting it tweaked, but I thought > it was going to land with a small modification. Clearly it hasn't yet. > Thanks for pointing it out. > > John > =:-> > > > On Sat, J

Re: bootstrap && status still down?

2014-06-14 Thread John Meinel
Ah, ok. I remembered reviewing that and wanting it tweaked, but I thought it was going to land with a small modification. Clearly it hasn't yet. Thanks for pointing it out. John =:-> On Sat, Jun 14, 2014 at 12:36 PM, Andrew Wilkins < andrew.wilk...@canonical.com> wrote: > On Sat, Jun 14, 2014 a

Re: Availability zone support

2014-06-14 Thread John Meinel
... > 2) If you have 2 services, you likely would rather them on the same AZ >> rather than spread across different AZ because of the different cost of >> network bandwidth. How do we manage multiple services? Do we just use a >> strictly deterministic ordering? (always sort the AZ names, round r

Re: bootstrap && status still down?

2014-06-14 Thread Andrew Wilkins
On Sat, Jun 14, 2014 at 12:41 PM, John Meinel wrote: > I just did "juju bootstrap" and then ran "juju status" afterwards. Note > that this was manual, so it wasn't a "juju bootstrap && juju status" > running it immediately after. However, I still saw: > $ juju status -e amz-jam > environment: amz

Re: bootstrap && status still down?

2014-06-14 Thread John Meinel
I did just try it again with the local provider, and I saw the same behavior: It is up, as I clearly wouldn't have anyone else to talk to: $ juju status -e local environment: local machines: "0": agent-state: down agent-state-info: (started) agent-version: 1.19.4.1 dns-name: loca

Re: Availability zone support

2014-06-14 Thread Andrew Wilkins
On Sat, Jun 14, 2014 at 12:16 PM, John Meinel wrote: > I think this is interesting, but there are a few bits of fallout we need > to consider. > > 1) Just today I failed to bootstrap trunk with: > 2014-06-14 04:11:47 ERROR juju.provider.common bootstrap.go:119 bootstrap > failed: cannot start boo