"unexpected number of interfaces in response from creating device" when retrying lxd containers that have multiple interfaces
Bug #1682338 reported by
John A Meinel
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
John A Meinel | ||
Bug Description
The bugfix for bug #1670873 was incomplete. It turns out to only work when the container requested has a single device.
The current code has a check that when "creating a device it has 1 network interface" and then creates the rest of the network interfaces.
The fix for bug #1670873 added a check that if the device already exists, don't try to create it, but *didn't* handle the case of devices that had more than one network interface, so it would try to set up all the extra interfaces, and always fails because the device is already set up.
| tags: | added: dtag |
| Changed in juju: | |
| importance: | Critical → High |
Revision history for this message
| John A Meinel (jameinel) wrote | #1 |
| Changed in juju: | |
| status: | Triaged → In Progress |
| Changed in juju: | |
| assignee: | nobody → John A Meinel (jameinel) |
| Changed in juju: | |
| status: | In Progress → Fix Committed |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
The actual bug hit someone in the field, but only as a consequence of a different problem (and fixing this particular bug wouldn't have actually fixed their underlying problem). So I'm downgrading it from High.
https:/
Should be a reasonable fix for this. It should be developed off of the 2.1 branch, just in case we want to release a 2.1.3 (they were hitting this in the field/they could always just merge it if they really needed it.)