[2.x, API] Creating a subnet with fabric specified gets the default fabric anyway
Bug #1701256 reported by
Данило Шеган
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
High
|
Mike Pontillo |
Bug Description
In noticing a problem with how defaults are handled with Django 1.11 (see https:/
However, that fails even with master: it still picks up the default fabric and default vlan from it.
summary: |
- Creating a subnet with fabric specified gets the default fabric anyway + [2.x, API] Creating a subnet with fabric specified gets the default + fabric anyway |
Changed in maas: | |
milestone: | none → 2.3.0 |
Changed in maas: | |
milestone: | 2.3.0 → 2.3.x |
Changed in maas: | |
milestone: | 2.3.x → 2.5.x |
assignee: | nobody → Mike Pontillo (mpontillo) |
To post a comment you must log in.
This bug has not seen any activity in the last 6 months, so it is being automatically closed.
If you are still experiencing this issue, please feel free to re-open.
MAAS Team