Async operation message popup: INFO message when accepted and success/error message when receiving a result

Bug #1286418 reported by Cindy Lu
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Fix Released
Wishlist
LIU Yulong

Bug Description

When you Create Volume successfully it should show the green "success" tooltip.

Instead, it currently shows the message on the blue "info" tooltip.

This is also the case for Volume "Create Snapshot".

Revision history for this message
David Lapsley (dlapsley) wrote :

Hi Cindy!

So.. the blue message is actually informational and gets called in openstack_dashboard.dashboards.project.volumes.forms.CreateForm.handle(). This part is performing as it should.

However, as you point out, no success message has been implemented for this function.

Cheers, David.

Revision history for this message
David Lapsley (dlapsley) wrote :

I believe the reason for this is because the view/form is not able to verify successful volume creation. It simply sends the API command and informs the user of this.

Volume creation even on devstack can take a few seconds for a small 1 GB volume. In production, it can take even longer (depending on the size of the volume). Once the command has been launched, horizon tracks the changing state of the new volume via the Status column which is updated via the DataTable/Ajax polling system. When the volume has completed the State changes from "Creating" to "Available".

I don't think there is a simple fix for this. As far as I can tell, this is working as designed.

Hope that helps!

Dave.

Revision history for this message
David Lapsley (dlapsley) wrote :

After thinking about this a bit more... we could trigger a success message based on the results received by client-side ajax polling function. This sounds more like a feature than a bug. If someone else would like to weigh in on the appropriate way to proceed, we can take it from there...

Cheers, Dave.

Revision history for this message
Cindy Lu (clu-m) wrote :

Hi Dave!

Thanks for looking into the issue. :)

Revision history for this message
Ana Malagon (atmalagon) wrote :

This bug: https://bugs.launchpad.net/horizon/+bug/1277257 is tangentially related re: success messages.

Revision history for this message
Akihiro Motoki (amotoki) wrote :

Summarizing the discussion above, generally speaking, it seems better to:
- Display an accepted message with INFO tooltip, and
- Display success or error message once a transient state finishes (in AJAX?)

tags: added: ux
summary: - Create Volume success message is displayed in blue info tooltip
+ Async operation message popup: Create Volume success message is
+ displayed in blue info tooltip
summary: - Async operation message popup: Create Volume success message is
- displayed in blue info tooltip
+ Async operation message popup: INFO message when accepted and
+ success/error message when receiving a result
Changed in horizon:
status: New → Confirmed
milestone: none → ongoing
Revision history for this message
Akihiro Motoki (amotoki) wrote :

bug 1291681 is a similar report.

Revision history for this message
Santiago Baldassin (santiago-b-baldassin) wrote :
Revision history for this message
Julie Pichon (jpichon) wrote :

Another bug that would probably benefit from this at https://bugs.launchpad.net/horizon/+bug/1326301

Julie Pichon (jpichon)
Changed in horizon:
importance: Undecided → Wishlist
tags: added: error-reporting
Changed in horizon:
assignee: nobody → LIU Yulong (dragon889)
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on horizon (master)

Change abandoned by David Lyle (<email address hidden>) on branch: master
Review: https://review.openstack.org/117718
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

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/268981

Changed in horizon:
assignee: LIU Yulong (dragon889) → Itxaka Serrano (itxakaserrano)
Changed in horizon:
assignee: Itxaka Serrano (itxakaserrano) → LIU Yulong (dragon889)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on horizon (master)

Change abandoned by Itxaka Serrano Garcia (<email address hidden>) on branch: master
Review: https://review.openstack.org/268981
Reason: Original patch was restored by owner at https://review.openstack.org/#/c/117718/ so continuing any work in there!

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to horizon (master)

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

commit d3dd5e0ff06a9c1e9fa7d7c1da6526f767479d4a
Author: LIU Yulong <email address hidden>
Date: Fri Aug 29 16:16:15 2014 +0800

    Make no response notification(msg) level to INFO

    Some API calls just sent but the results were uncertain,
    Horizon should notify the user that your request is
    just accepted, not successfully.
    So this patch change some form message level to INFO,
    and some message expression.

    Change-Id: I241cd9cf3ad6b2bd747e3ea1c6040a140ba77b56
    Closes-Bug: #1326301
    Closes-Bug: #1286418

Changed in horizon:
status: In Progress → Fix Released
Changed in horizon:
milestone: ongoing → 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.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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