maas-devel team mailing list archive

[Dhastha <dhasthagheer@xxxxxxxxx>]

The above error gone again I run with following command

juju bootstrap -e maas --upload-tools

Now , the status of one machine is "Allocated".

Now one more node is in still Ready state. How to allocate it to JUJU?

I did,

created one more MAAS key and added one paragraph

environments:
  maas:
    type: maas
   # Change this to where your MAAS server lives.  It must specify the
base path.
    maas-server: 'http://192.168.1.151/MAAS/'
    maas-oauth:
'EWEjxN6hdvtr7G5EMU:mM7rbkMaf2DYgSdfJb:CFMqduBQkNxbTzbRgffPC8HJHWQGAaxL'
    admin-secret: 'nothing'
    default-series: precise
    authorized-keys-path: ~/.ssh/id_rsa.pub # or any file you want.
    # Or:
    # authorized-keys: ssh-rsa keymaterialhere

  maas:
    type: maas
    # Change this to where your MAAS server lives.  It must specify
the base path.
    maas-server: 'http://192.168.1.151/MAAS/'
    maas-oauth:
'kYZg2mGZk8bKUssRzS:W5dqgkYcawNfGmjDZn:ndnyF2u4RcY4auhAeRpbxLXMdkwKF868'
    admin-secret: 'nothing'
    default-series: precise
    authorized-keys-path: ~/.ssh/id_rsa.pub # or any file you want.


Again I ran

juju bootstrap --upload-tools

is returns environment already bootstrapped. So please tell me how can
I allocate one more node to juju.

There is one button in MAAS web UI to start the node, It will allocate
to the user. Shall I use Web UI to allocate node? Will juju identify
it?

On Thu, Sep 26, 2013 at 12:36 PM, Dhastha <dhasthagheer@xxxxxxxxx> wrote:
> There is no issue with MAC address, MAAS have MAC address for the two
> node and its power type WOL .
>
> After commissioned the two nodes the status is Ready, then I am
> running the  command
>
> juju bootstrap -e maas
> error: Get https://juju-dist.s3.amazonaws.com/tools/juju-1.14.1-quantal-amd64.tgz:
> EOF
>
> My Internet connection is working fine and there is no proxy.
>
> How to solve this?
>
>
> On Thu, Sep 26, 2013 at 8:59 AM, Jeroen Vermeulen
> <jeroen.vermeulen@xxxxxxxxxxxxx> wrote:
>> On 25/09/13 18:38, Dhastha wrote:
>>>
>>> I am getting following error while i run
>>>
>>> sudo juju bootstrap
>>>
>>> error: cannot start bootstrap instance: gomaasapi: got error back from
>>> server: 403 FORBIDDEN (You are not allowed to start up this node.)
>>>
>>> I have two nodes which is in Ready state. Can any one help me to resolve
>>> this?
>>
>>
>> This might happen if MAAS does not have a MAC address for the node, or
>> possibly if Juju isn't logged into MAAS properly.  But there's another way.
>>
>> We have a known bug (bug 1223088 on Launchpad) where sometimes nodes, once
>> commissioned, are marked as having an owner.  If that owner is a different
>> one from the account under which your Juju environment logs into MAAS, you
>> won't be allowed to allocate it.
>>
>> You can check for this in the node's UI page: does it show an Owner?  If it
>> does, then you're hitting this problem.  Please let us know so we can
>> prioritize the bug.
>>
>> If this is what's happened, you should be able to reset the nodes to a
>> normal state by temporarily making the MAAS account that you use for your
>> Juju environment an administrator, allocating both nodes, and then taking
>> away administrator status again.
>>
>>
>> Jeroen
>>
>> --
>> 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
>
>
>
> --
>
>
>
>
> Cheers,
>
> Dhasthagheer
> Jr. Software Engineer
> Fundamental Research Group
> Indian Institute of Technology, Bombay



-- 




Cheers,

Dhasthagheer
Jr. Software Engineer
Fundamental Research Group
Indian Institute of Technology, Bombay