Bug 1453038 - Cannot create Cloud Volume from CFME web-interface
Summary: Cannot create Cloud Volume from CFME web-interface
Keywords:
Status: CLOSED DUPLICATE of bug 1442766
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: GA
: cfme-future
Assignee: Tzu-Mainn Chen
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-22 01:06 UTC by tachoi
Modified: 2020-07-16 09:36 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-22 23:10:34 UTC
Category: ---
Cloudforms Team: Openstack
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description tachoi 2017-05-22 01:06:53 UTC
Description of problem:
Creating volumes are stuck in "creating" state because of wrong ems selected.

Version-Release number of selected component (if applicable):
5.7.2.1

How reproducible:
Adding Openstack Provider
Creating Cloud volume from UI

Steps to Reproduce:
1.
2.
3.

Actual results:
Stuck in provisioning status

Expected results:
Creating cinder volume properly

Additional info:
Looking at cloud_volume_controller.rb, it seems like "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 request for creating volumes are stuck in "creating" state because of wrong ems.

[1]https://github.com/ManageIQ/manageiq/blob/euwe-2.1/app/controllers/cloud_volume_controller.rb#L289

Comment 2 ITD27M01 2017-05-22 15:00:38 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.