Unable to compose LXD VM with multiple NICs
Bug #1923246 reported by
Lee Trager
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Unassigned | ||
maas-ui |
Fix Released
|
Unknown
|
Bug Description
I used the UI to compose an LXD VM. In the UI I requested that the VM was created with two NICs. The UI even asked which space and subnet I want the NICs on.
1. The machine was composed with only 1 NIC, it silently ignored my request for a second NIC
2. During commissioning MAAS discovered my VM host has access to two networks 10.0.0.0/24 and 192.168.122.0/24. My deployment only had 10.0.0.0/24 configured, there was no configured access to 192.168.122.0/24. During composition the UI indicated I could have multiple NICs on either network even though no bridge was available to 192.168.112.0/24.
Changed in maas-ui: | |
importance: | Undecided → Unknown |
Changed in maas: | |
milestone: | 3.0.0-beta3 → 3.0.0-beta4 |
Changed in maas-ui: | |
status: | New → Fix Released |
Changed in maas: | |
status: | New → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Could you attach the content of the websocket request to compose the machine?
Also note that the backend to properly report available networks for LXD is still work in progress.