More meaningful message should be displayed when a conflict error occurred in ng-swift

Bug #1566820 reported by Kenji Ishii
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Fix Released
Medium
Kenji Ishii

Bug Description

When a user create/delete folder or object, it might occur a Conflict(or Already Exist) Error.
However, at the moment, the message displayed to users doesn't include this meaning.
Just display "Unable to create/delete xxx".
When we can know the cause of the error, we should display the message including that cause.

Kenji Ishii (ken-ishii)
Changed in horizon:
assignee: nobody → Kenji Ishii (ken-ishii)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to horizon (master)

Fix proposed to branch: master
Review: https://review.openstack.org/303350

Changed in horizon:
status: New → In Progress
Changed in horizon:
importance: Undecided → Medium
tags: added: error-reporting
Changed in horizon:
milestone: none → next
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to horizon (master)

Reviewed: https://review.openstack.org/303350
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=2327e9c1e1f2188f4229656791d589686fc66325
Submitter: Jenkins
Branch: master

commit 2327e9c1e1f2188f4229656791d589686fc66325
Author: Kenji Ishii <email address hidden>
Date: Fri Apr 8 10:33:09 2016 +0000

    Improve error message of when Conflict error occur in ng-swift

    When we create a container, folder or object, error will occur if the
    specified name is already exist. And when we delete, if specified
    container or folder have a content, error will occur.
    At the moment, error message is always same in all cases.
    This patch will improve the message of when Conflict exception occur.

    Change-Id: I825ef09badd1b10bb6fdab8f223bd6dfed28f3a4
    Closes-bug: #1566820

Changed in horizon:
status: In Progress → Fix Released
Changed in horizon:
milestone: next → newton-1
Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/horizon 10.0.0.0b1

This issue was fixed in the openstack/horizon 10.0.0.0b1 development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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