Re: JUJU bootstrap error
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 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 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
fx...@lenovo.com
Lenovo.com
Twitter | Facebook | Instagram | Blogs | Forums
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
--
Feng xia
Engineer
Lenovo USA
Phone: 5088011794
fx...@lenovo.com
Lenovo.com
Twitter | Facebook | Instagram | Blogs | Forums
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
Re: JUJU bootstrap error
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 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 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
fx...@lenovo.com
Lenovo.com
Twitter | Facebook | Instagram | Blogs | Forums
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
Re: JUJU bootstrap error
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 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 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
> fx...@lenovo.com
>
> Lenovo.com
> Twitter | Facebook | Instagram | Blogs | Forums
>
>
>
>
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
>>>
>>
>
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
Re: JUJU bootstrap error
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 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
fx...@lenovo.com
Lenovo.com
Twitter | Facebook | Instagram | Blogs | Forums
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
Re: JUJU bootstrap error
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 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
fx...@lenovo.com
Lenovo.com
Twitter | Facebook | Instagram | Blogs | Forums
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
Re: JUJU bootstrap error
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 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
fx...@lenovo.com
Lenovo.com
Twitter | Facebook | Instagram | Blogs | Forums
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
Re: JUJU bootstrap error
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 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
> fx...@lenovo.com
>
> Lenovo.com
> Twitter | Facebook | Instagram | Blogs | Forums
>
>
>
>
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
Re: JUJU bootstrap error
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
fx...@lenovo.com
Lenovo.com
Twitter | Facebook | Instagram | Blogs | Forums
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
Re: JUJU bootstrap error
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
fx...@lenovo.com
Lenovo.com
Twitter | Facebook | Instagram | Blogs | Forums
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
Re: JUJU bootstrap error
This is some more information:
juju clouds
CloudRegions Default TypeDescription
aws 14 us-east-1ec2 Amazon Web Services
aws-china 1 cn-north-1 ec2 Amazon China
aws-gov1 us-gov-west-1ec2 Amazon (USA Government)
azure 24 centralusazure Microsoft Azure
azure-china2 chinaeastazure Microsoft Azure China
cloudsigma 5 hnl cloudsigma CloudSigma Cloud
google 8 us-east1 gce Google Cloud Platform
joyent 6 eu-ams-1 joyent Joyent Cloud
oracle 5 uscom-central-1 oracle Oracle Compute Cloud
Service
rackspace 6 dfw rackspace Rackspace Cloud
localhost 1 localhostlxd LXD Container Hypervisor
*prodmaas 0 maasMetal As A Service*
the yaml file:
clouds:
prodmaas:
type: maas
auth-types: [oauth1]
endpoint: http://IP/MAAS
On 08/03/2017 04:39 PM, wahi wrote:
One additional infomration the JUJU version is 2.2
On 08/03/2017 04:08 PM, wahi wrote:
Hi Witod,
Thanks a lot for your response.
Nop the same error.
On 08/03/2017 04:04 PM, Witold Krecicki wrote:
Could you check if juju bootstrap maas-cloud maas-cloud-controller
--bootstrap-constraints mem=0 works?
On Thu, Aug 3, 2017 at 1:41 PM, wahi wrote:
Hi Christian,
Thanks for your reply.
Yes I am seeing the VM with 4GB from MAAS web UI.
On 08/03/2017 02:32 PM, Christian Muirhead wrote:
Hi Wahi -
Can you look in the MAAS web UI and confirm that MAAS can see the
4GB of
memory in the machine you expect? I've had a situation where I
added ram to
a KVM but forgot to re-enlist the machine or update the ram in MAAS.
Cheers,
Christian
On Thu., 3 Aug. 2017, 19:13 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
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
Re: JUJU bootstrap error
One additional infomration the JUJU version is 2.2
On 08/03/2017 04:08 PM, wahi wrote:
Hi Witod,
Thanks a lot for your response.
Nop the same error.
On 08/03/2017 04:04 PM, Witold Krecicki wrote:
Could you check if juju bootstrap maas-cloud maas-cloud-controller
--bootstrap-constraints mem=0 works?
On Thu, Aug 3, 2017 at 1:41 PM, wahi wrote:
Hi Christian,
Thanks for your reply.
Yes I am seeing the VM with 4GB from MAAS web UI.
On 08/03/2017 02:32 PM, Christian Muirhead wrote:
Hi Wahi -
Can you look in the MAAS web UI and confirm that MAAS can see the
4GB of
memory in the machine you expect? I've had a situation where I added
ram to
a KVM but forgot to re-enlist the machine or update the ram in MAAS.
Cheers,
Christian
On Thu., 3 Aug. 2017, 19:13 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
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
Re: JUJU bootstrap error
Hi Witod,
Thanks a lot for your response.
Nop the same error.
On 08/03/2017 04:04 PM, Witold Krecicki wrote:
Could you check if juju bootstrap maas-cloud maas-cloud-controller
--bootstrap-constraints mem=0 works?
On Thu, Aug 3, 2017 at 1:41 PM, wahi wrote:
Hi Christian,
Thanks for your reply.
Yes I am seeing the VM with 4GB from MAAS web UI.
On 08/03/2017 02:32 PM, Christian Muirhead wrote:
Hi Wahi -
Can you look in the MAAS web UI and confirm that MAAS can see the 4GB of
memory in the machine you expect? I've had a situation where I added ram to
a KVM but forgot to re-enlist the machine or update the ram in MAAS.
Cheers,
Christian
On Thu., 3 Aug. 2017, 19:13 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
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
Re: JUJU bootstrap error
Could you check if juju bootstrap maas-cloud maas-cloud-controller
--bootstrap-constraints mem=0 works?
On Thu, Aug 3, 2017 at 1:41 PM, wahi wrote:
> Hi Christian,
>
> Thanks for your reply.
>
> Yes I am seeing the VM with 4GB from MAAS web UI.
>
>
> On 08/03/2017 02:32 PM, Christian Muirhead wrote:
>
> Hi Wahi -
> Can you look in the MAAS web UI and confirm that MAAS can see the 4GB of
> memory in the machine you expect? I've had a situation where I added ram to
> a KVM but forgot to re-enlist the machine or update the ram in MAAS.
> Cheers,
> Christian
>
>
> On Thu., 3 Aug. 2017, 19:13 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
>>
>> --
>> Juju mailing list
>> Juju@lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju
>
>
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
Re: JUJU bootstrap error
Hi Christian,
Thanks for your reply.
Yes I am seeing the VM with 4GB from MAAS web UI.
On 08/03/2017 02:32 PM, Christian Muirhead wrote:
Hi Wahi -
Can you look in the MAAS web UI and confirm that MAAS can see the 4GB
of memory in the machine you expect? I've had a situation where I
added ram to a KVM but forgot to re-enlist the machine or update the
ram in MAAS.
Cheers,
Christian
On Thu., 3 Aug. 2017, 19:13 wahi, mailto:w...@sci.am>>
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
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
Re: JUJU bootstrap error
Hi Wahi -
Can you look in the MAAS web UI and confirm that MAAS can see the 4GB of
memory in the machine you expect? I've had a situation where I added ram to
a KVM but forgot to re-enlist the machine or update the ram in MAAS.
Cheers,
Christian
On Thu., 3 Aug. 2017, 19:13 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
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
JUJU bootstrap error
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
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju bootstrap error
juju contacts that server in attempt to download the binaries it uses for agents on machines. you avoid the lookup and download there by using juju bootstrap --upload-tools On Fri, May 23, 2014 at 8:46 AM, boyd yang wrote: > Hi David, > > The error still exists after few days. > Why does the juju bootstrap need to communicate to that server? > > > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > Reading package lists... > Building dependency tree... > Reading state information... > cpu-checker is already the newest version. > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > Reading package lists... > Building dependency tree... > Reading state information... > bridge-utils is already the newest version. > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > Reading package lists... > Building dependency tree... > Reading state information... > rsyslog-gnutls is already the newest version. > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > Reading package lists... > Building dependency tree... > Reading state information... > juju-mongodb is already the newest version. > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > curl: (56) SSL read: error::lib(0):func(0):reason(0), errno 104 > tools from > https://streams.canonical.com/juju/tools/releases/juju-1.18.3-trusty-amd64.tgzdownloaded: > HTTP 200; time 1692.359s; size 6979584 bytes; speed 4124.000 > bytes/s 2014-05-23 11:32:09 ERROR juju.provider.common bootstrap.go:123 > bootstrap failed: rc: 1 > Stopping instance... > 2014-05-23 11:32:09 ERROR juju.cmd supercommand.go:305 rc: 1 > > > On Wed, May 21, 2014 at 6:46 PM, David Cheney > wrote: > >> I am sorry, the bootstrap machine was not able to communicate with the >> server, streams.canonical.com. Please try again, I hope this error is >> temporary. >> >> On Wed, May 21, 2014 at 7:32 PM, boyd yang wrote: >> > Hello, >> > >> > Juju bootstrap gives below error: >> > ... >> > bridge-utils is already the newest version. >> > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. >> > Reading package lists... >> > Building dependency tree... >> > Reading state information... >> > rsyslog-gnutls is already the newest version. >> > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. >> > Reading package lists... >> > Building dependency tree... >> > Reading state information... >> > juju-mongodb is already the newest version. >> > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. >> > curl: (56) SSL read: error::lib(0):func(0):reason(0), errno 104 >> > tools from >> https://streams.canonical.com/juju/tools/releases/juju-1.18.3-trusty-amd64.tgz >> > downloaded: HTTP 200; time 1471.629s; size 7094272 bytes; speed >> > 4820.000 bytes/s 2014-05-21 08:29:45 ERROR juju.provider.common >> > bootstrap.go:123 bootstrap failed: rc: 1 >> > Stopping instance... >> > 2014-05-21 08:29:45 ERROR juju.cmd supercommand.go:305 rc: 1 >> > >> > -- >> > Juju mailing list >> > Juju@lists.ubuntu.com >> > Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/juju >> > > > -- > Juju mailing list > Juju@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju bootstrap error
Hi David, The error still exists after few days. Why does the juju bootstrap need to communicate to that server? 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Reading package lists... Building dependency tree... Reading state information... cpu-checker is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Reading package lists... Building dependency tree... Reading state information... bridge-utils is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Reading package lists... Building dependency tree... Reading state information... rsyslog-gnutls is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Reading package lists... Building dependency tree... Reading state information... juju-mongodb is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. curl: (56) SSL read: error::lib(0):func(0):reason(0), errno 104 tools from https://streams.canonical.com/juju/tools/releases/juju-1.18.3-trusty-amd64.tgzdownloaded: HTTP 200; time 1692.359s; size 6979584 bytes; speed 4124.000 bytes/s 2014-05-23 11:32:09 ERROR juju.provider.common bootstrap.go:123 bootstrap failed: rc: 1 Stopping instance... 2014-05-23 11:32:09 ERROR juju.cmd supercommand.go:305 rc: 1 On Wed, May 21, 2014 at 6:46 PM, David Cheney wrote: > I am sorry, the bootstrap machine was not able to communicate with the > server, streams.canonical.com. Please try again, I hope this error is > temporary. > > On Wed, May 21, 2014 at 7:32 PM, boyd yang wrote: > > Hello, > > > > Juju bootstrap gives below error: > > ... > > bridge-utils is already the newest version. > > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > Reading package lists... > > Building dependency tree... > > Reading state information... > > rsyslog-gnutls is already the newest version. > > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > Reading package lists... > > Building dependency tree... > > Reading state information... > > juju-mongodb is already the newest version. > > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > curl: (56) SSL read: error::lib(0):func(0):reason(0), errno 104 > > tools from > https://streams.canonical.com/juju/tools/releases/juju-1.18.3-trusty-amd64.tgz > > downloaded: HTTP 200; time 1471.629s; size 7094272 bytes; speed > > 4820.000 bytes/s 2014-05-21 08:29:45 ERROR juju.provider.common > > bootstrap.go:123 bootstrap failed: rc: 1 > > Stopping instance... > > 2014-05-21 08:29:45 ERROR juju.cmd supercommand.go:305 rc: 1 > > > > -- > > Juju mailing list > > Juju@lists.ubuntu.com > > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju bootstrap error
I made a bug for the rc: 1 error message: https://bugs.launchpad.net/juju-core/+bug/1321793 I've looked at it in the past, but wasn't able to devote enough time to actually make it report something useful. On Wed, May 21, 2014 at 9:56 AM, Nate Finch wrote: > Ug we really need to clean up our error reporting in this area. rc: 1 > is a completely unacceptable error message. > > > On Wed, May 21, 2014 at 6:46 AM, David Cheney > wrote: > >> I am sorry, the bootstrap machine was not able to communicate with the >> server, streams.canonical.com. Please try again, I hope this error is >> temporary. >> >> On Wed, May 21, 2014 at 7:32 PM, boyd yang wrote: >> > Hello, >> > >> > Juju bootstrap gives below error: >> > ... >> > bridge-utils is already the newest version. >> > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. >> > Reading package lists... >> > Building dependency tree... >> > Reading state information... >> > rsyslog-gnutls is already the newest version. >> > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. >> > Reading package lists... >> > Building dependency tree... >> > Reading state information... >> > juju-mongodb is already the newest version. >> > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. >> > curl: (56) SSL read: error::lib(0):func(0):reason(0), errno 104 >> > tools from >> https://streams.canonical.com/juju/tools/releases/juju-1.18.3-trusty-amd64.tgz >> > downloaded: HTTP 200; time 1471.629s; size 7094272 bytes; speed >> > 4820.000 bytes/s 2014-05-21 08:29:45 ERROR juju.provider.common >> > bootstrap.go:123 bootstrap failed: rc: 1 >> > Stopping instance... >> > 2014-05-21 08:29:45 ERROR juju.cmd supercommand.go:305 rc: 1 >> > >> > -- >> > Juju mailing list >> > Juju@lists.ubuntu.com >> > Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/juju >> >> -- >> Juju mailing list >> Juju@lists.ubuntu.com >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/juju >> > > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju bootstrap error
Ug we really need to clean up our error reporting in this area. rc: 1 is a completely unacceptable error message. On Wed, May 21, 2014 at 6:46 AM, David Cheney wrote: > I am sorry, the bootstrap machine was not able to communicate with the > server, streams.canonical.com. Please try again, I hope this error is > temporary. > > On Wed, May 21, 2014 at 7:32 PM, boyd yang wrote: > > Hello, > > > > Juju bootstrap gives below error: > > ... > > bridge-utils is already the newest version. > > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > Reading package lists... > > Building dependency tree... > > Reading state information... > > rsyslog-gnutls is already the newest version. > > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > Reading package lists... > > Building dependency tree... > > Reading state information... > > juju-mongodb is already the newest version. > > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > curl: (56) SSL read: error::lib(0):func(0):reason(0), errno 104 > > tools from > https://streams.canonical.com/juju/tools/releases/juju-1.18.3-trusty-amd64.tgz > > downloaded: HTTP 200; time 1471.629s; size 7094272 bytes; speed > > 4820.000 bytes/s 2014-05-21 08:29:45 ERROR juju.provider.common > > bootstrap.go:123 bootstrap failed: rc: 1 > > Stopping instance... > > 2014-05-21 08:29:45 ERROR juju.cmd supercommand.go:305 rc: 1 > > > > -- > > Juju mailing list > > Juju@lists.ubuntu.com > > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > > -- > Juju mailing list > Juju@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju bootstrap error
I am sorry, the bootstrap machine was not able to communicate with the server, streams.canonical.com. Please try again, I hope this error is temporary. On Wed, May 21, 2014 at 7:32 PM, boyd yang wrote: > Hello, > > Juju bootstrap gives below error: > ... > bridge-utils is already the newest version. > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > Reading package lists... > Building dependency tree... > Reading state information... > rsyslog-gnutls is already the newest version. > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > Reading package lists... > Building dependency tree... > Reading state information... > juju-mongodb is already the newest version. > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > curl: (56) SSL read: error::lib(0):func(0):reason(0), errno 104 > tools from > https://streams.canonical.com/juju/tools/releases/juju-1.18.3-trusty-amd64.tgz > downloaded: HTTP 200; time 1471.629s; size 7094272 bytes; speed > 4820.000 bytes/s 2014-05-21 08:29:45 ERROR juju.provider.common > bootstrap.go:123 bootstrap failed: rc: 1 > Stopping instance... > 2014-05-21 08:29:45 ERROR juju.cmd supercommand.go:305 rc: 1 > > -- > Juju mailing list > Juju@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
juju bootstrap error
Hello, Juju bootstrap gives below error: ... bridge-utils is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Reading package lists... Building dependency tree... Reading state information... rsyslog-gnutls is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Reading package lists... Building dependency tree... Reading state information... juju-mongodb is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. curl: (56) SSL read: error::lib(0):func(0):reason(0), errno 104 tools from https://streams.canonical.com/juju/tools/releases/juju-1.18.3-trusty-amd64.tgz downloaded: HTTP 200; time 1471.629s; size 7094272 bytes; speed 4820.000 bytes/s 2014-05-21 08:29:45 ERROR juju.provider.common bootstrap.go:123 bootstrap failed: rc: 1 Stopping instance... 2014-05-21 08:29:45 ERROR juju.cmd supercommand.go:305 rc: 1 -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
