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
Fix Released
Fix Released

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 and My deployment only had configured, there was no configured access to During composition the UI indicated I could have multiple NICs on either network even though no bridge was available to

Tags: ui
Revision history for this message
Alberto Donato (ack) wrote :

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.

Changed in maas:
status: Triaged → Incomplete
Revision history for this message
Lee Trager (ltrager) wrote :

It looks like the UI isn't passing the full form :\


tags: added: ui
Changed in maas:
status: Incomplete → New
Changed in maas-ui:
importance: Undecided → Unknown
Revision history for this message
Alberto Donato (ack) wrote :

Yeah the "interfaces" field is empty, which means default to a single interface in the "best guessed" network

Changed in maas:
milestone: 3.0.0-beta3 → 3.0.0-beta4
Changed in maas-ui:
status: New → Fix Released
Alberto Donato (ack)
Changed in maas:
status: New → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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