[UI, UX] Bad error message when failing to create a range because another already exists
Bug #1608559 reported by
Andres Rodriguez
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
High
|
Unassigned | ||
2.0 |
Won't Fix
|
High
|
Unassigned |
Bug Description
From https:/
"The IPRange could not be created because the data didn't validate."
This is a bad error message
description: | updated |
Changed in maas: | |
milestone: | 2.1.0 → 2.1.1 |
Changed in maas: | |
milestone: | 2.1.1 → 2.1.2 |
Changed in maas: | |
milestone: | 2.1.2 → 2.1.3 |
Changed in maas: | |
milestone: | 2.1.3 → 2.3.x |
To post a comment you must log in.
I have not been able to reproduce this issue. I believe this has been fixed by other related branches that have already landed. If able to reproduce, please provide the steps so I can take another look.