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
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
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
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, wah
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=
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 res
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
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 0
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
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 Amazo
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
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 re
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 wro
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 r
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 al
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 ju
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 vers
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 ou
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 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 versi
20 matches
Mail list logo
