maas-devel team mailing list archive
-
maas-devel team
-
Mailing list archive
-
Message #00121
Re: MAAS Testing
On Fri, Apr 20, 2012 at 11:09 AM, Michael Hughes <itismike@xxxxxxxxx> wrote:
> Nice catch Francis. That was a c/p error on my part. After editing
> that file what do I need to do to refresh the parameters?
>
You can try juju bootstrap again. It'll catch the changes in your
environment.yaml files automatically, but since your nodes are in
somewhat broken state due to maas shell commands I asked you to run,
it might not work or you might run into the ProtocolError again you
pasted.
> On Fri, Apr 20, 2012 at 9:03 AM, Diogo Matsubara
> <matsubara@xxxxxxxxxxxxx> wrote:
>> On Fri, Apr 20, 2012 at 11:02 AM, Michael Hughes <itismike@xxxxxxxxx> wrote:
>>> Hi Francis. Here's my environments.yaml file:
>>>
>>> $ cat ~/.juju/environments.yaml
>>> environments:
>>> maas:
>>> type: maas
>>> maas-server: 'http://172.23.1.1/MAAS:80/MAAS'
>>
>> This should be 'http://172.23.1.1:80/MAAS
>>
>>> maas-oauth: 'fQzecEPwaZmHjPF9YM:Mx[..]5CAfGH3qSmh2KWeepcMZy3d4s7CX'
>>> admin-secret: 'nothing'
>>> default-series: precise
>>>
>>>
>>> On Fri, Apr 20, 2012 at 8:58 AM, Francis J. Lacoste
>>> <francis.lacoste@xxxxxxxxxxxxx> wrote:
>>>> On 12-04-19 12:22 PM, Michael Hughes wrote:
>>>>> Thanks Diogo! I added the reference to the Ephemeral bug to the troubleshooter.
>>>>>
>>>>> Verbose provides a few more lines at the bottom:
>>>>> ~$ juju --verbose bootstrap
>>>>> 2012-04-19 10:43:15,254 DEBUG Initializing juju bootstrap runtime
>>>>> ...
>>>>> Traceback (most recent call last):
>>>>> Failure: juju.errors.ProviderInteractionError: Unexpected TimeoutError
>>>>> interacting with provider: User timeout caused connection failure.
>>>>> 2012-04-19 10:43:45,297 ERROR Traceback (most recent call last):
>>>>> Failure: juju.errors.ProviderInteractionError: Unexpected TimeoutError
>>>>> interacting with provider: User timeout caused connection failure.
>>>>>
>>>>> Unexpected TimeoutError interacting with provider: User timeout caused
>>>>> connection failure.
>>>>> 2012-04-19 10:43:45,299 ERROR Unexpected TimeoutError interacting with
>>>>> provider: User timeout caused connection failure.
>>>>> ~$
>>>>>
>>>>
>>>> What is maas-server set to in your .juju/environment.yaml file. Make
>>>> sure, that the hostname/IP you use there can be reached by the network
>>>> on which the nodes run. Basically, you need a URL that will work for
>>>> both the juju client and the juju agents on the nodes running in the MAAS.
>>>>
>>>> (For example, that's why http://localhost is never going to work.)
>>>>
>>>> Cheers
>>>>
>>>> --
>>>> Francis J. Lacoste
>>>> francis.lacoste@xxxxxxxxxxxxx
>>>>
>>>>
>>>> --
>>>> Mailing list: https://launchpad.net/~maas-devel
>>>> Post to : maas-devel@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~maas-devel
>>>> More help : https://help.launchpad.net/ListHelp
>>>>
>>>
>>> --
>>> Mailing list: https://launchpad.net/~maas-devel
>>> Post to : maas-devel@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~maas-devel
>>> More help : https://help.launchpad.net/ListHelp
>>
>>
>>
>> --
>> Diogo M. Matsubara
--
Diogo M. Matsubara
Follow ups
References
-
MAAS Testing
From: Michael Hughes, 2012-04-17
-
Re: MAAS Testing
From: Francis J. Lacoste, 2012-04-17
-
Re: MAAS Testing
From: Michael Hughes, 2012-04-17
-
Re: MAAS Testing
From: Francis J. Lacoste, 2012-04-17
-
Re: MAAS Testing
From: Michael Hughes, 2012-04-18
-
Re: MAAS Testing
From: Michael Hughes, 2012-04-18
-
Re: MAAS Testing
From: Jeroen Vermeulen, 2012-04-19
-
Re: MAAS Testing
From: Michael Hughes, 2012-04-19
-
Re: MAAS Testing
From: Diogo Matsubara, 2012-04-19
-
Re: MAAS Testing
From: Diogo Matsubara, 2012-04-19
-
Re: MAAS Testing
From: Michael Hughes, 2012-04-19
-
Re: MAAS Testing
From: Francis J. Lacoste, 2012-04-20
-
Re: MAAS Testing
From: Michael Hughes, 2012-04-20
-
Re: MAAS Testing
From: Diogo Matsubara, 2012-04-20
-
Re: MAAS Testing
From: Michael Hughes, 2012-04-20