Known bug, though I thought the fix made it into 1.19.1.
To work around it, you use
juju bootstrap --upload-tools --series precise, trusty
John
=:-
On Apr 25, 2014 9:35 PM, Asif Iqbal vad...@gmail.com wrote:
I am using 1.19.1-trusty-amd64, installed from ppa:juju/devel
I am failing start
On Sun, Apr 27, 2014 at 4:31 PM, José Antonio Rey j...@ubuntu.com wrote:
Or set default-series: precise on your environments.yaml file
It is setup like that
local:
type: local
default-series: precise
units still showing pending
1:
instance-id: pending
series: precise
Was it like that before you bootstrapped?
On 04/27/2014 03:34 PM, Asif Iqbal wrote:
On Sun, Apr 27, 2014 at 4:31 PM, José Antonio Rey j...@ubuntu.com
mailto:j...@ubuntu.com wrote:
Or set default-series: precise on your environments.yaml file
It is setup like that
local:
The peergrouper thing is a non fatal problem with the local provider (it is
only used for HA which is currently disabled for local). The problem with
default series is the local provider defaults to only making tools for your
host available (trusty). Which is why you specify the extra tools series
On Sun, Apr 27, 2014 at 4:50 PM, John Meinel j...@arbash-meinel.com wrote:
The peergrouper thing is a non fatal problem with the local provider (it
is only used for HA which is currently disabled for local). The problem
with default series is the local provider defaults to only making tools
Maybe you haven't destroyed your environment and re-bootstrapped?
On 04/27/2014 03:55 PM, Asif Iqbal wrote:
On Sun, Apr 27, 2014 at 4:50 PM, John Meinel j...@arbash-meinel.com
mailto:j...@arbash-meinel.com wrote:
The peergrouper thing is a non fatal problem with the local provider
I don't quite understand the rush each time to break backwards
compatibility. I guess Go doesn't let you have compile time flags, so if
you want to use any new functionality there's no good way to do it
optionally.
Anyway, as long as 1.2 gets backported to Precise and Saucy we could do so.
I
