[2.3] Toggling Subnet from Managed to Unmanaged doesn't warn the user that behavior changes

Bug #1696270 reported by Christian Reis
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Mike Pontillo

Bug Description

When you enable Managed Allocation on a subnet, MAAS hands out IP addresses from the dynamic range to handle any dynamic DHCP request -- including the ephemeral environment. In this mode, you use Reserved Ranges to ensure that MAAS does not touch those IP addresses.

When you disable Managed Allocation, the semantics seem to toggle, and MAAS will take IP addresses from the reserved range and allocate those to machines. This has caused problems where we took over IP addresses of network infrastructure after toggling the option.

Related branches

Changed in maas:
milestone: none → 2.3.0
importance: Undecided → High
status: New → Triaged
assignee: nobody → Maria Vrachni (m-vrachnis)
summary: - Managed Allocation dangerously toggles the semantics for Reserved Ranges
+ [2.3] Managed Allocation dangerously toggles the semantics for Reserved
+ Ranges
summary: - [2.3] Managed Allocation dangerously toggles the semantics for Reserved
- Ranges
+ [2.3] Toggling Subnet from Managed to Unmanaged doesn't warn the user
+ that behavior changes
Revision history for this message
Kevin (thenewmanium) wrote :

+1 here. The behavior and semantics are super confusing when it comes to Reserved Ranges and Managed Allocation mode.

Changed in maas:
assignee: Maria Vrachni (m-vrachnis) → Mike Pontillo (mpontillo)
status: Triaged → In Progress
milestone: 2.3.0 → 2.3.0beta1
Changed in maas:
status: In Progress → 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.