check how we model VLAN devices
Bug #1652049 reported by
John A Meinel
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Expired
|
High
|
Unassigned | ||
Bug Description
ATM it seems we model a VLAN tagged device as being a NIC that has a vlan tag (which we don't seem to track?) that has a "ParentName" of the underlying ethernet device. However, we also use "ParentName" to track when a device is on a bridge.
We should make sure we have a clear and understandable representation of each device type, so we don't have to do weird checks when determining what devices could be bridged to provide access for containers.
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #1 |
| Changed in juju: | |
| status: | Triaged → Expired |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.