MAAS Region controller (regionA.maas) is running up, synched with one Rack Controller (rackA.maas), who has actually one node (nodeA02.maas) with address: 192.168.1.38:2225.
Had a first automatic commissioning on friday evening (wasn't in office when happend) with nodeA02.maas. Meanwhile this node went back to commissioning failed, and I've no more access to nodeA02.maas.
Tried to restart one right after the other:
- first regionA.maas (region controller)
- second rackA.maas (rack controller)
- third nodeA02.maas
nodeA02.maasis booting under MAAS -> Great!!, this is what I tried to do.
But terminal shows up login credential created my MAAS as the most well know screen:
Ubuntu 16.04.02 LTS ubuntu tty1
Ubuntu Login: _
MY QUESTION NOW:
How may I access to nodeA02.maas, if I haven't log in credentials?
TO SPECIFY
All SSH keys (public keys) where added to MAAS before this actually situation.
I searched/googled around, but wasn't successful in finding some useful stuff. Maybe someone with experience in this?
My actually most closes reads are these:
What is the MAAS node login?
What username/password does MAAS assign to nodes?
MAAS boots inaccessible nodes when there's no SSH registered for a given user
problem with authentication via SSH on MaaS Nodes
Any of these provides useful stuff that worked for me.
virsh. – Gianni May 26 '17 at 13:19virsh, so to be able to manage nodes virtually. I'm pretty shure you can help out this issue. :D – Gianni May 29 '17 at 10:29