Horizon doesn't notify when fail to attach a volume

Bug #1340197 reported by Yogev Rabl
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Invalid
Undecided
srividyaketharaju

Bug Description

Description of problem:
Horizon doesn't notify when the attachment of volume process fail with Errors.
The nova-compute log show errors during the process of the volume attachment but the Horizon doesn't present the failure and the error.

Version-Release number of selected component (if applicable):
python-django-horizon-2014.1-7.el7ost.noarch
openstack-nova-network-2014.1-7.el7ost.noarch
python-novaclient-2.17.0-2.el7ost.noarch
openstack-nova-common-2014.1-7.el7ost.noarch
openstack-nova-compute-2014.1-7.el7ost.noarch
openstack-nova-conductor-2014.1-7.el7ost.noarch
openstack-nova-scheduler-2014.1-7.el7ost.noarch
openstack-nova-api-2014.1-7.el7ost.noarch
openstack-nova-cert-2014.1-7.el7ost.noarch
openstack-nova-novncproxy-2014.1-7.el7ost.noarch
python-nova-2014.1-7.el7ost.noarch
openstack-nova-console-2014.1-7.el7ost.noarch

How reproducible:
100%

Steps to Reproduce:
1. Follow the step of the bug: https://bugs.launchpad.net/nova/+bug/1340169
2. In the Horizon try to attach a volume

Actual results:
The Horizon shows an info message:
Info: Attaching volume bowl-the-dust to instance cougar-01-fe5510a5-c50c-46ee-9d71-6f8e41a58ecc on /dev/vdc.

The volume status changes to 'attaching' then change back to available.

Expected results:
An error should appear saying "Error: the volume attachment failed"

Additional info:
The Horizon log is attached.
The nova-compute log with the volume attachment error is available in the bug https://bugs.launchpad.net/nova/+bug/1340169

Revision history for this message
Yogev Rabl (yrabl) wrote :
Revision history for this message
Julie Pichon (jpichon) wrote :

Cinder actions are asynchronous, meaning Horizon can only see that the command was sent successfully but not yet what the result is. There's an open bug to make these messages be INFO level rather than SUCCESS at bug 1286418, I'm not sure there is not much else we can do in the meantime (until maybe we get real time communication implemented).

Changed in horizon:
importance: Undecided → Wishlist
Revision history for this message
Julie Pichon (jpichon) wrote :

There is also this blueprint although it hasn't received much attention: https://blueprints.launchpad.net/cinder/+spec/return-error-messages-to-horizon .

Changed in horizon:
assignee: nobody → srividyaketharaju (srividya)
Revision history for this message
Vishal Manchanda (vishalmanchanda) wrote :

Hi, this bug looks quite old. I am not able to reproduce it in the master branch.
Please find below the steps how I tried to reproduce it:

1. I have updated the status for a volume(name= test).
2. Then If I try to attach to a nova instance, I get an error in the horizon.
I have also attached a screenshot for the same.
So I am changing this bug status to invalid. Feel free to open it if you are still facing the same issue
and add the steps to reproduce it.

Changed in horizon:
status: New → Invalid
importance: Wishlist → Undecided
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.