LXD VM fails composing

Bug #1959905 reported by Dan Ardelean
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
High
Alexsander de Souza

Bug Description

Creating LXD VMs fails.

1. In MAAS 3.1, I've deployed a black machine with Ubuntu 20.04, no LXD host yet. I've added br0 on eth0 as instructed in here https://maas.io/docs/snap/3.1/ui/how-to-manage-vm-hosts#heading--maas-bridge-web-ui

2. I've connected to the LXD host and did `lxd init` as described in here https://maas.io/docs/snap/3.1/ui/how-to-use-lxd#heading--lxd-setup

Here are some logs https://pastebin.ubuntu.com/p/NmxYH3vFv6/

3. Added the Ubuntu machine as a LXD host in MAAS. Here are some logs
https://pastebin.ubuntu.com/p/8tFgpWz4f9/

So far so good, I can see the VM host from MAAS.

4. The LXD VM hangs in commissioning state.

The VM does note take any IP https://pastebin.ubuntu.com/p/v3SK4ZR8dp/

From the LXD host, I can see the DHCP process (discover, offer, request, ack), so the packets should arrive to the VM https://pastebin.ubuntu.com/p/jjdrffyDpM/

Logs from MAAS https://pastebin.ubuntu.com/p/bK55wGXPpK/

Tags: training
description: updated
tags: added: training
Changed in maas:
assignee: nobody → Alexsander de Souza (alexsander-souza)
status: New → In Progress
milestone: none → next
importance: Undecided → High
Revision history for this message
Alexsander de Souza (alexsander-souza) wrote :

Hi,

I need more details to reproduce this issue:

- the hosts are physical servers or VMs?
- what's the topology of the network connecting these hosts?
- can you tgz the whole /var/snap/maas/common/log dir and share with me?

thanks

Revision history for this message
Dan Ardelean (danardelean) wrote :

Hi, here are the info you've asked for and the logs.

https://pastebin.ubuntu.com/p/vCbTcNXWB6/

Revision history for this message
Dan Ardelean (danardelean) wrote :

Yep, seems like it was an env issue. You can close the bug. Thanks.

Changed in maas:
status: In Progress → Invalid
Changed in maas:
milestone: next → 3.2.0-beta1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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