MAAS

juju status returns ERROR Invalid SSH Key

Asked by John Barbee

I have been able to successfully 'juju bootstrap', but I am stuck with 'juju status' here is what I got the first time I ran it.

Please type 'yes' or 'no': The authenticity of host 'node-003048c0cd2a.mydomain.com (172.16.1.71)' can't be established.
ECDSA key fingerprint is f8:02:18:7c:24:b6:99:20:cc:ab:29:d0:bc:c4:d7:20.
Are you sure you want to continue connecting (yes/no)? yes
2012-05-22 05:55:55,411 ERROR Invalid SSH key
2012-05-22 05:56:24,390 ERROR Invalid SSH key
2012-05-22 05:56:54,623 ERROR Invalid SSH key

Before running bootstrap or status, I created my ssh keys and added the generated public key to the preferences of my user account on the MAAS UI.

Any ideas why I am getting this SSH error?

Question information

Language:
English Edit question
Status:
Answered
For:
MAAS Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Julian Edwards (julian-edwards) said : 		#1

Have the nodes finished installing?

Revision history for this message
John Barbee (jbarbee00) said : 		#2

Yes, this error still occurs hours after the nodes install.

Revision history for this message
David Medberry (med) said : 		#3

Any chance you edited the bootstrap node name from the MAAS node interface?

Revision history for this message
Julian Edwards (julian-edwards) said : 		#4

Is your DNS still pointing in the right place?

Revision history for this message
John Barbee (jbarbee00) said : 		#5

David

I have not changed the names of any nodes.

Julian

DNS is correct. I can ping the FQDN of the nodes in the web UI.

Revision history for this message
Ray Wang (raywang) said : 		#6

It's same here.
DNS works, System is installed, fingerprint is accepted.

Revision history for this message
Launchpad Janitor (janitor) said : 		#7

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Julian Edwards (julian-edwards) said : 		#8

One more thing - are the clocks reasonably accurate on the maas server and on the nodes? If they are too far out of sync, it makes OAuth fail which currently silently breaks the metadata access from the commissioning node, which makes it just sit at a login prompt instead of finishing the commissioning process and rebooting.

Can you help with this problem?

Provide an answer of your own, or ask John Barbee for more information if necessary.

To post a message you must log in.