Hi Feng, what method were you using to ssh to the Juju node? When you bootstrap with juju it will grab local ssh keys to setup for the ubuntu user on the juju managed nodes. For example, I temporarily removed my ssh key from my MAAS user profile and bootstrapped from my laptop a new controller and I was able to ssh to the controller with 'juju switch controller && juju ssh 0'. This uses the local keys I have on my laptop system.
If you want to not use juju ssh then you need to specify the ubuntu user name on the images. On my MAAS the address of machine 0 is 10.0.0.8 ssh ubuntu@10.0.0.8 Does that not work for you? On Fri, May 19, 2017 at 8:12 AM fengxia <fx...@lenovo.com> wrote: > Hi Juju, > > I ran into an issue which I couldn't figure out. I setup a MAAS > controller, can manually provision node directly using MAAS and was able > to ssh to it, so I suppose MAAS is all working well. > > Then if I use $ juju deploy to start a node, I could not ssh to this > node. What is the right way to access this node? > > -- > Feng xia > Engineer > Lenovo USA > > Phone: 5088011794 <(508)%20801-1794> > 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
