"Failed to login to virsh console" error while composing a machine using pod on another node
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Undecided
|
Björn Tillenius |
Bug Description
I have a MAAS 2.8 version installed on one of my nodes. Configured it with 2 KVM pods. One pod connects to virsh on the same node where MAAS is hosted. The second KVM pod is hosted on another node (server).
I have add the required SSH keys in MAAS and am able to add a pod but composing a machine fails. If I keep on retrying my attempts, at times it goes through. Not sure if there are any other settings missing.
When I checked the rackd logs, it shows this error:
2021-09-02 04:52:26 provisioningser
Traceback (most recent call last):
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
current.result = callback(
File "/usr/lib/
_inlineCal
--- <exception caught here> ---
File "/usr/lib/
result = result.
File "/usr/lib/
return g.throw(self.type, self.value, self.tb)
File "/usr/lib/
conn = yield self.get_
File "/usr/lib/
result = g.send(result)
File "/usr/lib/
raise VirshError("Failed to login to virsh console.")
provisioningse
MAAS Version: 2.8
Ubuntu version: 18.04
virsh version: 4.0.0
I have a bridge interface (br0) added and attached to the virsh as a network.
Let me know if any other information is required.
Hi there, to make sure I understand, you have 2 host machines, 1 of those hosts is running MAAS and both hosts are running virsh? And the host running MAAS and virsh can connect but MAAS cannot connect to the remote host?
Are there multiple routes between the two host machines? And is it possible there are firewall rules for one or more of those routes but not all?