← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1494166] [NEW] Error message is not specific and distinct when the Qos Spec name already exist

 

Public bug reported:

When input a "QoS Spec" name that already exist in create "QoS Spec" modal form, we will see the error message: "Unable to create QoS Spec" in the top right corner of the page, this error message is not specific and clear.
If we provide specific and clear error message: 'QoS Spec name "%s" already exists.' beside the name field,  it will be more better.

** Affects: horizon
     Importance: Undecided
         Status: New

** Description changed:

- When input a "QoS Spec" name that already exist in create "QoS Spec" modal form, we will see the error message: "Unable to create QoS Spec", this error message is not specific and clear.
- If provide specific and clear error message: 'QoS Spec name "%s" already exists.' beside the name field,  it will be more better.
+ When input a "QoS Spec" name that already exist in create "QoS Spec" modal form, we will see the error message: "Unable to create QoS Spec" in the top right corner of the page, this error message is not specific and clear.
+ If we provide specific and clear error message: 'QoS Spec name "%s" already exists.' beside the name field,  it will be more better.

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1494166

Title:
  Error message is not specific and distinct when the  Qos Spec name
  already exist

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  When input a "QoS Spec" name that already exist in create "QoS Spec" modal form, we will see the error message: "Unable to create QoS Spec" in the top right corner of the page, this error message is not specific and clear.
  If we provide specific and clear error message: 'QoS Spec name "%s" already exists.' beside the name field,  it will be more better.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1494166/+subscriptions


Follow ups