[UI, UX] MAAS doesn't tell the user if a dynamic range was already created when trying to enable DHCP.
Bug #1608557 reported by
Andres Rodriguez
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Steve Rydz | ||
Bug Description
When you already have a dynamic range, and you try to enable DHCP, MAAS doesn't tell the user that the range already exists:
1. Go to Subnet, create Dynamic range.
2. Go the VLAN, and "Provide DHCP".
3. UI won't tell you that there are dynamic ranges already created or which ones are those.
Related branches
~steverydz/maas:dhcp-take-two
- Anthony Dillon: Approve
- Blake Rouse (community): Approve
- MAAS Lander: Approve
-
Diff: 1889 lines (+1057/-508)9 files modifiedsrc/maasserver/static/js/angular/controllers/dashboard.js (+2/-18)
src/maasserver/static/js/angular/controllers/tests/test_vlan_details.js (+497/-191)
src/maasserver/static/js/angular/controllers/vlan_details.js (+233/-93)
src/maasserver/static/js/angular/directives/ipranges.js (+35/-0)
src/maasserver/static/js/angular/services/manager.js (+17/-0)
src/maasserver/static/partials/ipranges.html (+14/-11)
src/maasserver/static/partials/subnet-details.html (+0/-5)
src/maasserver/static/partials/vlan-details.html (+258/-190)
src/maasserver/static/scss/_utils.scss (+1/-0)
| tags: | added: ui ux |
| Changed in maas: | |
| importance: | Undecided → High |
| milestone: | none → 2.1.0 |
| Changed in maas: | |
| status: | New → Confirmed |
| Changed in maas: | |
| status: | Confirmed → Triaged |
| Changed in maas: | |
| milestone: | 2.0.1 → 2.3.x |
| Changed in maas: | |
| assignee: | nobody → Martin Storey (cassiocassio) |
Revision history for this message
| Lilyana Videnova (lilyanavidenova) wrote | #1 |
| Changed in maas: | |
| assignee: | Martin Storey (cassiocassio) → Steve Rydz (steverydz) |
| Changed in maas: | |
| status: | Triaged → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This will be fixed with the new design: https:/