JUJU bootstrap error

[fengxia]

I think your old SSH won't work anymore.

Instead, at juju CLI terminal, find the machine number, say machine 1, 
that corresponds to your VM, then

$ juju ssh 1

During the provisioning process, juju creates its own credentials so 
your MAAS ssh is not relevant. That's my understanding.


On 08/03/2017 02:36 PM, wahi wrote:
> I was trying to ssh from the MAAS server as when the VM was deployed. 
> and got ssh key permission error.
>
> But it worked as you have suggested.
>
> Thank you.
>
>
> On 08/03/2017 10:34 PM, Witold Krecicki wrote:
>> What do you mean by 'not working'? What's the error message?
>> You can try connecting to it by using juju ssh -m controller 0
>>
>>
>> On Thu, Aug 3, 2017 at 8:24 PM, wahi <wahi at sci.am> wrote:
>>> One and final question.
>>>
>>> When I released the node and deployed it once again, the ssh 
>>> connection with
>>> it not working, it was working before releasing, I think it is 
>>> something
>>> related to ssh known hosts keys etc how can I adjust it ?
>>>
>>> Thank you very much once again.
>>>
>>>
>>>
>>> On 08/03/2017 10:12 PM, wahi wrote:
>>>> Yes indeed the situation is much better now:
>>>>
>>>> juju bootstrap maas-cloud maas-cloud-controller
>>>> Creating Juju controller "maas-cloud-controller" on maas-cloud
>>>> Looking for packaged Juju agent version 2.2.2 for amd64
>>>> Launching controller instance(s) on maas-cloud...
>>>>   - hwgnpw (arch=amd64 mem=4G cores=2)
>>>> Fetching Juju GUI 2.7.5
>>>> Waiting for address
>>>> Attempting to connect to 10.0.17.7:22
>>>> sudo: unable to resolve host node5
>>>> Bootstrap agent now started
>>>> Contacting Juju controller at 10.0.17.7 to verify accessibility...
>>>> Bootstrap complete, "maas-cloud-controller" controller now available.
>>>> Controller machines are in the "controller" model.
>>>> Initial model "default" added.
>>>>
>>>> Do I need to add public IP to this VM in order to use JUJU 
>>>> controller web
>>>> UI.
>>>>
>>>> And thank you very much for all suggestions and help.
>>>>
>>>>
>>>> On 08/03/2017 10:02 PM, wahi wrote:
>>>>> I released the VM now and erasing the disk, I will try to 
>>>>> bootstrap and
>>>>> update the status.
>>>>>
>>>>>
>>>>> On 08/03/2017 09:55 PM, Witold Krecicki wrote:
>>>>>> It has to be ready and available for juju - it'll take care of 
>>>>>> deploying
>>>>>> it.
>>>>>>
>>>>>> On Thu, Aug 3, 2017 at 7:48 PM, wahi <wahi at sci.am> wrote:
>>>>>>> Hi Fengxia,
>>>>>>>
>>>>>>> Thanks for your response.
>>>>>>>
>>>>>>> Actually the VM is deployed already by MAAS, do I need to 
>>>>>>> commission it
>>>>>>> and
>>>>>>> not go to the deployment ? is the deployment will be by JUJU ?
>>>>>>>
>>>>>>>
>>>>>>> On 08/03/2017 06:23 PM, fengxia wrote:
>>>>>>>
>>>>>>> Another thing to check. Is your VM in the "READY" state?
>>>>>>>
>>>>>>>
>>>>>>> On 08/03/2017 03:12 AM, wahi wrote:
>>>>>>>
>>>>>>> Dear all,
>>>>>>>
>>>>>>>
>>>>>>> Recently I am investingating the installation of Openstack using 
>>>>>>> MAAS
>>>>>>> and
>>>>>>> JUJU.
>>>>>>>
>>>>>>> I installaed MAAS on bare metals server Ubuntu 16.04, I have 
>>>>>>> another
>>>>>>> server
>>>>>>> also which has Ubuntu 16.04.
>>>>>>>
>>>>>>> I managed to deploy several KVM virtual machines on two servers 
>>>>>>> using
>>>>>>> MAAS,
>>>>>>> so every VM got private IP address form MAAS.
>>>>>>>
>>>>>>>
>>>>>>> I installed JUJU package on a VM which is located on the second 
>>>>>>> server
>>>>>>> (not
>>>>>>> MAAS server), from there I did the following steps:
>>>>>>>
>>>>>>> juju add-cloud /here I chose MAAS/
>>>>>>>
>>>>>>> Here: Enter the API endpoint url: 
>>>>>>> http://public_IP_OF_MAAS:5240/MAAS
>>>>>>>
>>>>>>> juju bootstrap maas-cloud
>>>>>>>
>>>>>>> juju clouds /maas-cloud is there/
>>>>>>>
>>>>>>> juju add-credential maas-cloud /Entered the API key/
>>>>>>>
>>>>>>> juju bootstrap maas-cloud maas-cloud-controller
>>>>>>>
>>>>>>> after this command getting
>>>>>>>
>>>>>>> Creating Juju controller "prodmaas-controller" on prodmaas
>>>>>>>
>>>>>>> Looking for packaged Juju agent version 2.0.2 for amd64
>>>>>>>
>>>>>>> Launching controller instance(s) on prodmaas...
>>>>>>>
>>>>>>> ERROR failed to bootstrap model: cannot start bootstrap instance:
>>>>>>> cannot run
>>>>>>> instances: cannot run instance: No available machine matches
>>>>>>> constraints:
>>>>>>> [('zone', ['default']), ('agent_name',
>>>>>>> ['f7a273ac-6190-4798-8ee6-f7d2df722b27']), ('mem', ['3584'])] 
>>>>>>> (resolved
>>>>>>> to
>>>>>>> "mem=3584.0 zone=default")
>>>>>>>
>>>>>>>
>>>>>>> I need to mention that I have a VM on MAAS server with 4GB 
>>>>>>> memory!!! (I
>>>>>>> don’t know if the error related to that)
>>>>>>>
>>>>>>>
>>>>>>> Could you please help me to identify the problem.
>>>>>>>
>>>>>>>
>>>>>>> Thank you very much in advance.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Wahi
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> -- 
>>>>>>> Feng xia
>>>>>>> Engineer
>>>>>>> Lenovo USA
>>>>>>>
>>>>>>> Phone: 5088011794
>>>>>>> fxia1 at lenovo.com
>>>>>>>
>>>>>>> Lenovo.com
>>>>>>> Twitter | Facebook | Instagram | Blogs | Forums
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> -- 
>>>>>>> Juju mailing list
>>>>>>> Juju at lists.ubuntu.com
>>>>>>> Modify settings or unsubscribe at:
>>>>>>> https://lists.ubuntu.com/mailman/listinfo/juju
>>>>>>>
>
>

-- 
Feng xia
Engineer
Lenovo USA

Phone: 5088011794
fxia1 at lenovo.com
  	
Lenovo.com
Twitter | Facebook | Instagram | Blogs | Forums