Deleting volume from Horizon system is returning 404 NOT FOUND

[Sergii Turivnyi]

Steps to reproduce:
 1. Navigate to horison as admin
 2. Navigate to tab Compute-> Volumes
 3. Click button "Create Volume"
 4. In the opened window click button "Create Volume".
 5. After volume is created click button "Delete Volume"
 6. Check Requests in browser console

Expected results:
No Errors

Actual result:
system is returning 404 NOT FOUND

[Sergey Kolekonov (skolekonov)]

Please clarify MOS version and provide diagnostic snapshot

[Sergei Chipiga (schipiga)]

As I know, it's default behavior to detect that object is deleted.

[Sergii Turivnyi (sturivnyi)]

With all due respect, to return 404 NOT FOUND to detect that object is deleted is not permissible.

[Sergii Turivnyi (sturivnyi)]

cat /etc/fuel_build_id:
 495
cat /etc/fuel_build_number:
 495
cat /etc/fuel_release:
 9.0
cat /etc/fuel_openstack_version:
 mitaka-9.0
rpm -qa | egrep 'fuel|astute|network-checker|nailgun|packetary|shotgun':
 fuel-release-9.0.0-1.mos6349.noarch
 fuel-misc-9.0.0-1.mos8460.noarch
 python-packetary-9.0.0-1.mos140.noarch
 fuel-bootstrap-cli-9.0.0-1.mos285.noarch
 fuel-migrate-9.0.0-1.mos8460.noarch
 shotgun-9.0.0-1.mos90.noarch
 fuel-notify-9.0.0-1.mos8460.noarch
 nailgun-mcagents-9.0.0-1.mos750.noarch
 python-fuelclient-9.0.0-1.mos325.noarch
 fuel-9.0.0-1.mos6349.noarch
 fuel-utils-9.0.0-1.mos8460.noarch
 fuel-setup-9.0.0-1.mos6349.noarch
 fuel-provisioning-scripts-9.0.0-1.mos8743.noarch
 fuel-library9.0-9.0.0-1.mos8460.noarch
 network-checker-9.0.0-1.mos74.x86_64
 fuel-agent-9.0.0-1.mos285.noarch
 fuel-ui-9.0.0-1.mos2717.noarch
 fuel-ostf-9.0.0-1.mos936.noarch
 fuelmenu-9.0.0-1.mos274.noarch
 fuel-nailgun-9.0.0-1.mos8743.noarch
 rubygem-astute-9.0.0-1.mos750.noarch
 fuel-mirror-9.0.0-1.mos140.noarch
 fuel-openstack-metadata-9.0.0-1.mos8743.noarch

[Sergii Turivnyi (sturivnyi)]

Snapshot
https://drive.google.com/open?id=0B8hkiEm94sEtWk1WeWpfcWR4ZkE

[Timur Sufiev (tsufiev-x)]

Works as intended from Horizon POV - currently it uses polling to detect if an object still exists, and it is expected for Cinder API to return 404 code for an object which no longer exists. We expect this to be fixed not sooner than a new way of notification is implemented in Horizon, and given that no one is working on this, this is definitely not going to happen in any foreseeable future.