[2.5rc2] Cannot communicate with KVM hosts if stale SSH fingerprint is cached
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Medium
|
Newell Jensen |
Bug Description
Hello everybody !
I am experimenting with 2.5-RC2 and I am trying to deploy a node as a KVM pod.
The installation is fresh with only 1 user, 1 domain, and dozen nodes.
I have attempted multiple times to deploy and invariably falls and stops on the cloud-init message :
Cloud-init v. 18.4-0ubuntu1~
ci-info: no authorized ssh keys fingerprints found for user virsh.
Cloud-init v. 18.4-0ubuntu1~
Then Web UI indicates the deployment has failed and the node is errored.
All is seemingly install however and the network is configured properly too.
Would anybody have any idea what is happening ?
Best wishes,
Florian
Related branches
- Newell Jensen (community): Approve
-
Diff: 155 lines (+57/-8)5 files modifieddebian/maas-common.install (+5/-0)
scripts/unverified-ssh (+9/-0)
setup.py (+3/-2)
src/provisioningserver/drivers/pod/tests/test_virsh.py (+32/-6)
src/provisioningserver/drivers/pod/virsh.py (+8/-0)
- Andres Rodriguez (community): Approve
- Mike Pontillo (community): Approve
- MAAS Lander: Pending (unittests) requested
-
Diff: 155 lines (+57/-8)5 files modifieddebian/maas-common.install (+5/-0)
scripts/unverified-ssh (+9/-0)
setup.py (+3/-2)
src/provisioningserver/drivers/pod/tests/test_virsh.py (+32/-6)
src/provisioningserver/drivers/pod/virsh.py (+8/-0)
Changed in maas: | |
status: | Incomplete → Triaged |
importance: | Undecided → Medium |
summary: |
- [2.5rc2] Deploy as KVM pod fails with missing key fingerprints for virsh + [2.5rc2] Cannot communicate with KVM hosts if stale SSH fingerprint is + cached |
Changed in maas: | |
assignee: | nobody → Newell Jensen (newell-jensen) |
Changed in maas: | |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
Hi Florian,
COuld you please provide full installation logs and machine cloud-init logs:
rsyslog: /var/log/ maas/rsyslog/ <machine- name>/date/ messages cloud-init. log,cloud- init-output. log #from the system itself. (the "deployed" one)
machine cloud-init logs: /var/log/