Subnets-> Reserved->Purpose - Rephrase migration message
Bug #1585666 reported by
Maria Vrachni
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Mike Pontillo | ||
| 2.0 |
Won't Fix
|
High
|
Mike Pontillo | ||
Bug Description
On subnets details page, in the Reserved table the user can see a message such as the following:
Migrated from static range: 10.0.4.1-10.0.4.255 on 10.0.0.0/16.
Current result:
Given I’m on a subnets details page
When I am reading the Purpose column in the Reserved table
Then I am unable to understand the purpose for the reserved IPs for migration
Expected/ correct result:
Given I’m on a subnets details page
When I am reading the Purpose column in the Reserved table
Then I should be able to understand the purpose for the reserved IPs for migration (rephrase the message please)
Details:
The user testing showed that meaning of the message is unclear to the user.
Related branches
lp:~blake-rouse/maas/fix-networking-add-ui
- Mike Pontillo (community): Approve
-
Diff: 1825 lines (+544/-973)14 files modifiedsrc/maasserver/static/css/maas-styles.css (+1/-1)
src/maasserver/static/js/angular/controllers/networks_list.js (+60/-153)
src/maasserver/static/js/angular/controllers/tests/test_networks_list.js (+298/-224)
src/maasserver/static/js/angular/directives/maas_obj_form.js (+13/-5)
src/maasserver/static/js/angular/directives/model_field.js (+0/-159)
src/maasserver/static/js/angular/directives/tests/test_maas_obj_form.js (+37/-1)
src/maasserver/static/js/angular/directives/tests/test_model_field.js (+0/-331)
src/maasserver/static/partials/networks-list.html (+88/-89)
src/maasserver/static/partials/space-details.html (+2/-2)
src/maasserver/static/partials/subnet-details.html (+8/-6)
src/maasserver/static/scss/maas/components/_forms.scss (+4/-1)
src/maasserver/views/combo.py (+0/-1)
src/maasserver/websockets/handlers/tests/test_vlan.py (+20/-0)
src/maasserver/websockets/handlers/vlan.py (+13/-0)
lp:~mpontillo/maas/fix-iprange-migration-message--bug-1585666
- Gavin Panella (community): Approve
-
Diff: 14 lines (+1/-3)1 file modifiedsrc/maasserver/migrations/builtin/maasserver/0021_nodegroupinterface_to_iprange.py (+1/-3)
Revision history for this message
| Maria Vrachni (m-vrachnis) wrote | #1 |
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| milestone: | none → 2.0.0 |
| Changed in maas: | |
| assignee: | nobody → Maria Vrachni (m-vrachnis) |
Revision history for this message
| Carla Berkers (carlaberkers) wrote | #2 |
Revision history for this message
| Blake Rouse (blake-rouse) wrote | #3 |
| Changed in maas: | |
| assignee: | Maria Vrachni (m-vrachnis) → nobody |
| assignee: | nobody → Blake Rouse (blake-rouse) |
| Changed in maas: | |
| assignee: | Blake Rouse (blake-rouse) → Mike Pontillo (mpontillo) |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
We just discussed in our design review, and came up with the following solution. Description in the range table can be "Migrated from MAAS 1.x"
When a user clicks delete range, we will amend the error message to: "Ensure all in-use IP addresses are registered in MAAS before releasing this range to avoid potential collisions. Are you sure you want to delete this range?"