Created attachment 1280653 [details] screenshot Description of problem: Hi guys. In cloud_volume_controller.rb "def create" function [1] uses wrong external_management_system - association from cloud tenant that essentially is cloud provider whose type is "ManageIQ::Providers::Openstack::CloudManager" but cloud volumes should be created by "ManageIQ::Providers::StorageManager::CinderManager" ems. In this way all requests for creating volumes are stuck in "creating" state because of wrong ems. See attachment. [1]https://github.com/ManageIQ/manageiq/blob/euwe-2.1/app/controllers/cloud_volume_controller.rb#L289 Version-Release number of selected component (if applicable): [root@srv-os-cfme01 vmdb]# cat VERSION 5.7.2.1 How reproducible: Steps to Reproduce: 1. Add OpenStack cloud provider with cinder configured. 2. Try to add new cloud volume Actual results: requests for creating volumes are stuck in "creating" state because of wrong ems Expected results: Able to create new cloud volume from CFME. Additional info:
I apologize for not quite accurate information. Cloud volume eventually created. But one hangs in the creating state and the second appears as available: vmdb_production=# select id,name,status,ems_ref,ems_id from cloud_volumes; id | name | status | ems_ref | ems_id -----+-------------+-----------+--------------------------------------+-------- 97 | srv7-wagagu | available | bf50e1d3-251e-495e-b2d4-e116013e66cc | 1 96 | srv7-anene | in-use | 24af128b-9173-4660-b520-5b93f550e5b1 | 1 128 | srv7-nccs | in-use | 07c7ffb8-f3f6-4fe2-b6a7-6e30b40dd5a6 | 1 141 | test_ems_id | creating | bb64a46a-93c1-4c0c-bf61-5ed1fc87fd9f | 3 142 | test_ems_id | available | bb64a46a-93c1-4c0c-bf61-5ed1fc87fd9f | 1 (5 rows) Please pay attention to ems_id.
Ah, this is actually a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1441469, and should be fixed in the 5.8 release. Thanks! *** This bug has been marked as a duplicate of bug 1441469 ***