Enlistment error says I can login with ubuntu:ubuntu, but I can't

Bug #1409948 reported by Jason Hobbs
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Invalid
High
Unassigned

Bug Description

When a p8 node I have fails to enlist, it outputs to console that I can login with ubuntu:ubuntu and touch /tmp/block-poweroff. However, when I try to ssh in, I get an authentication failure (public key denied).

https://pastebin.canonical.com/123242/

the maas-enlist script tries to set the ubuntu user password but it doesn't work for some reason. I had to manually edit the enlistment userdata to add a public key to get this to work.

This is with MAAS 1.7.1~rc1+bzr3313-0ubuntu1~trusty1

Tags: oil
Revision history for this message
Blake Rouse (blake-rouse) wrote :

I think the best thing to do here is to not fix the message but fix the implementation. Meaning I think enlist should create the ubuntu user with the ubuntu password and allow a user to login before it restarts or restart after a minute. If the user logs in then it should stop the poweroff.

Thoughts?

Changed in maas:
status: New → Incomplete
Revision history for this message
Jason Hobbs (jason-hobbs) wrote :

Yes, that sounds reasonable to me. Perhaps a more secure solution would be to add public keys from the admin user in MAAS to the node.

Revision history for this message
Blake Rouse (blake-rouse) wrote :

Maybe but I think in most cases the user would be watching the node boot from a KVM or something. So password authentication would be the best.

Changed in maas:
status: Incomplete → Triaged
importance: Undecided → High
milestone: none → next
Revision history for this message
Mark Shuttleworth (sabdfl) wrote :

I like the idea of enabling SSH access for MAAS admin users in this case. MAAS already has root on this box ;)

I am currently experiencing this error first-hand in the gMAAS, because one of my nodes is failing to enlist for unknown reasons.

Revision history for this message
Andres Rodriguez (andreserl) wrote :

Hi!

**This is an automated message**

We believe this is no longer an issue in the latest MAAS releases. As such, we are marking this bug report as invalid. If you believe this is still an issue, please re-open this bug report.

Thanks

Changed in maas:
status: Triaged → Invalid
Changed in maas:
milestone: next → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.