MAAS

[UI, UX] Bad error message when failing to create a range because another already exists

Bug #1608559 reported by Andres Rodriguez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
High
Unassigned
MAAS 2.3.x
2.0
Won't Fix
High
Unassigned

Bug Description

From https://bugs.launchpad.net/maas/+bug/1608555, the error surfaced in the UI is:

"The IPRange could not be created because the data didn't validate."

This is a bad error message

See original description
Andres Rodriguez (andreserl)
description: updated
Andres Rodriguez (andreserl)
Changed in maas:
milestone: 2.1.0 → 2.1.1
Blake Rouse (blake-rouse)
Changed in maas:
milestone: 2.1.1 → 2.1.2
Revision history for this message
Newell Jensen (newell-jensen) wrote :

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.

Andres Rodriguez (andreserl)
Changed in maas:
milestone: 2.1.2 → 2.1.3
Andres Rodriguez (andreserl)
Changed in maas:
milestone: 2.1.3 → 2.3.x
Revision history for this message
Andres Rodriguez (andreserl) wrote :

Hi!

**This is an automated message**

We believe this is may no longer be an issue in the latest MAAS release. Due to the original date of the bug report, we are currently marking it as Invalid. If you believe this bug report still valid against the latest release of MAAS, or if you are still interested in this, please re-open this bug report.

Thanks

Changed in maas:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.