[2.5] Registering a KVM host provides insufficient debugging information on failure

[Mike Pontillo]

After attempting to deploy a KVM host with MAAS, I was presented with a "Failed deployment" message. In the regiond.log, I found the following exception:

https://paste.ubuntu.com/p/4FdFS7W9Yh/

This does not provide enough information to diagnose the problem. We should consider the following:

(1) Is it possible to add additional retries to the KVM host deployment process?
(2) Can we add additional logging in failure cases, such as which IP address was chosen as the pod URL, and the IP addresses configured on the machine?
(3) Should we try additional URLs in case of firewall issues?
(4) Should we consider more opinionated ways to designate network spaces? For example, if we know that a particular space is for network management rather than data plane traffic, that's likely to be a better space to select for network management purposes.

I didn't expect any retries to be necessary here, since we already have a "sleep 10" at the end of the array of "runcmd" options in the cloud-init vendor-data we use for deploying KVM hosts. It may be possible that a different race condition is interfering with the completed deployment, though.

[Thiago Martins (martinx)]

I just installed MaaS 2.5 beta 4, I can deploy Ubuntu 18.04 Machines normally, but, when I click to deploy the machine "As a KVM Host", it fails and I can't easily find why.

[Andres Rodriguez (andreserl)]

Debugging ifnormation should be available in:

1. On the machine itself: /var/log/cloud-init.log and /var/log/cloud-init-output.log
2. On MAAS: /var/log/maas/rsyslog/<machine-name>/<date>/messages

[Thiago Martins (martinx)]

I just found the problem!

https://paste.ubuntu.com/p/kWQd6Jwvrz/ - line 22

The generated Netplan yaml file is broken, no IPs!

---
    bridges:
        br-eno1:
            addresses:
            - None/22
            gateway4: 192.168.4.1
---

I'll post the logs soon!

[Thiago Martins (martinx)]

Netplan file

[Thiago Martins (martinx)]

The cloud-init.log

[Thiago Martins (martinx)]

And the cloud-init-output.log.

[Thiago Martins (martinx)]

It works with basic network topology (i.e., no BOND), however, when there is a BOND channel, the deployment fail again but, in a different stage.

So, here is what I'm trying to do (worth to mention that KVM Host deployments works without bond and with static IP on PXE network).

First try with manually configured BOND via MaaS Interfaces page, worked:
https://imgur.com/a/d2woB5f

Now, machine Released, trying as KVM Host on top of same BOND that just worked (above), but, failed later on:
https://imgur.com/a/sX0vD0g

It failed! But looks like that the machine was deployed correctly:
https://imgur.com/a/92OJeFq

Weird...

[Thiago Martins (martinx)]

New Netplan with BOND (works without KVM Host selected, as per first screenshot above):

[Thiago Martins (martinx)]

The cloud-init.log with BOND (failed deployment):

[Thiago Martins (martinx)]

The cloud-init.log with BOND (failed deployment):

[Thiago Martins (martinx)]

The cloud-init.log with BOND (failed deployment):

[Thiago Martins (martinx)]

The cloud-init-output.log (failed deployment):

[Adam Collard (adam-collard)]

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team