maas-devel team mailing list archive

[Michael Hughes <itismike@xxxxxxxxx>]

Hi Julian. Thanks for catching that. I mistakenly entered vi command
characters inside the string. After resolving that MAAS still wasn't
working so I rebuilt.

I'm succeeding to the point of deploying mysql and it went fine (no
errors,) but MAAS refuses to acknowledge my second node (NODE2-DD27)
is running:

$ juju status
2012-04-26 08:40:24,362 INFO Connecting to environment...
2012-04-26 08:40:25,672 INFO Connected to environment.
machines:
  0:
    agent-state: running
    dns-name: NODE1-86F0
    instance-id: /MAAS/api/1.0/nodes/node-c5500a72-f0dd-11e1-91d8-088e02002735/
    instance-state: unknown
  1:
    agent-state: not-started
    dns-name: NODE2-DD27
    instance-id: /MAAS/api/1.0/nodes/node-dee7c086-8edf-1271-bb60-0802f01e0035/
    instance-state: unknown
services:
  mysql:
    charm: cs:precise/mysql-0
    relations: {}
    units:
      mysql/0:
        agent-state: pending
        machine: 1
        public-address: null
2012-04-26 08:40:25,932 INFO 'status' command finished successfully

-Mike

On Mon, Apr 23, 2012 at 9:20 PM, Julian Edwards
<julian.edwards@xxxxxxxxxxxxx> wrote:
> On Monday 23 April 2012 10:15:25 Michael Hughes wrote:
>> Hi MAAS devels,
>>
>> I'm picking up where I left off last week and am hitting another
>> roadblock. MAAS is up and I have (up to) 5 servers running on it, all
>> showing in the GUI as "READY." But when I try to get Juju running I
>> receive the following:
>>
>> $ juju bootstrap
>> 2012-04-23 09:31:46,809 INFO Bootstrapping environment 'maas' (origin:
>> distro type: maas)...
>> Bootstrap aborted because file storage is not writable: The supplied
>> storage credentials were not accepted by the server
>> 2012-04-23 09:31:47,174 ERROR Bootstrap aborted because file storage
>> is not writable: The supplied storage credentials were not accepted by
>> the server
>>
>> Verbose output is here: http://pastebin.ubuntu.com/942569/
>>
>> Seems credential-related but from our discussions last week I
>> understand that I don't have to enter the ssh-key anywhere, just the
>> maas-oauth into the .juju/environments.yaml file, right?
>
> It looks like your maas credentials are out of date - can you check that the
> token you are using in the environments.yaml is the same as the one in the
> user preferences page?
>
> --
> 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