Created attachment 1365816 [details] Unexpected error Description of problem: ---------------------- Repetitive deletion of storage volume gives an unexpected error in UI. with undefined method `status' for nil:NilClass [cloud_volume/button] Version-Release number of selected component (if applicable): ------------------------------------------------------------ Version 5.7.4.2.20171207173836_e563ef4 How reproducible: ----------------- always Steps to Reproduce: ------------------- 1. create one storage volume 2. delete it one time 3. It will take time to delete; Now without refresh relationship go for deletion again. Actual results: --------------- Unexpected error Expected results: ----------------- It should handle this in the backend with proper UI flash message. Additional info: --------------- [0] Attaching snapshot [1] production log: http://pastebin.test.redhat.com/539438
Nikhil, Which provider is this for? Thanks Bronagh
The UI component to the error was previously fixed with https://github.com/ManageIQ/manageiq-providers-openstack/pull/147 However, the attempted second deletion was still triggering an error on the back end task. https://github.com/ManageIQ/manageiq-providers-openstack/pull/224 resolves the task error.
New commit detected on ManageIQ/manageiq-providers-openstack/master: https://github.com/ManageIQ/manageiq-providers-openstack/commit/46c702b6f879aef04f423ff9bd34e5f9acc06de2 commit 46c702b6f879aef04f423ff9bd34e5f9acc06de2 Author: Scott Seago <sseago> AuthorDate: Mon Feb 5 09:57:58 2018 -0500 Commit: Scott Seago <sseago> CommitDate: Mon Feb 5 14:10:03 2018 -0500 Bug 1524309 - Repetitive storage volume deletion gives unexpected error` BZ 1524309: handle "volume doesn't exist" situation in raw_delete_volume: https://bugzilla.redhat.com/show_bug.cgi?id=1524309 app/models/manageiq/providers/openstack/cloud_manager/cloud_volume.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Verified with Version 5.10.0.2.20180626170006_40dc459.
Verified on 5.10.0.3
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:0212