[2.3, snap] Snap uses /root/.ssh/known_hosts

Bug #1735536 reported by Andres Rodriguez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Triaged
Medium
Unassigned
2.3
Won't Fix
Medium
Unassigned

Bug Description

I re-deployed my MAAS environment from the snap, and was trying to re-connect to a machine that was running a pod, which I had also redeployed.

MAAS was unable to connect to the pod (and it wouldn't show why), and after a while, I realized that /root/.ssh/known_hosts had a fingerprint entry for a old deployment of the node.

This was making MAAS failing to ssh into the machine because the fingerprint didn't match and couldn't verify the node.

Tags: snap
Changed in maas:
milestone: none → 2.4.x
Changed in maas:
status: New → Triaged
importance: Undecided → Medium
Changed in maas:
milestone: 2.4.x → 2.5.0beta2
Changed in maas:
milestone: 2.5.0beta2 → 2.5.0rc1
Changed in maas:
milestone: 2.5.0rc1 → 2.5.x
Changed in maas:
milestone: 2.5.x → 2.5.0rc1
Changed in maas:
milestone: 2.5.0rc1 → 2.5.0
Changed in maas:
milestone: 2.5.0 → 2.5.x
Revision history for this message
Raphael Derosso Pereira (raphaelpereira) wrote :

This is also happening when you redeploy any machine that gets the same IP address as one that has been released. The errors are quite difficult to associate with this problem (known_hosts file).

In my case the problem was in file at /var/lib/maas/.ssh/known_hosts after trying to redeploy a machine with the new 2.5+ KVM host install feature.

Changed in maas:
milestone: 2.5.x → 2.6.0
tags: added: snap
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.