Bug 1566877

Summary: Repetitive Storage Managers
Product: Red Hat CloudForms Management Engine Reporter: Nikhil Dhandre <ndhandre>
Component: ProvidersAssignee: Marek Aufart <maufart>
Status: CLOSED NOTABUG QA Contact: Omri Hochman <ohochman>
Severity: high Docs Contact:
Priority: high    
Version: 5.9.0CC: cpelland, gblomqui, hkataria, jfrey, jhardy, lavenel, maufart, mpovolny, ndhandre, obarenbo
Target Milestone: GA   
Target Release: 5.9.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-18 06:50:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: Openstack Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Block Manager none

Description Nikhil Dhandre 2018-04-13 06:35:57 UTC 
Description of problem:
-----------------------
repetitive storage managers in UI

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


How reproducible:
-----------------
100%

Steps to Reproduce:
1. Navigate to Storage Manager Block or Object

Actual results:
---------------
two storage managers display one with cap and other with the small provider name.
like:
1. rhos11 Swift Manager
2. RHOS11 Swift Manager

Expected results:
-----------------
It should not


Additional info:
----------------
Attaching screenshots
Comment 6 Marek Aufart 2018-04-13 14:21:30 UTC 
The situation is that each OpenStack Cloud provider has its Storage Manager. There are two providers, so there also 2 Storage Managers (RHOS 11 and rhos 11).

Currently RHOS 11 and rhos 11 Providers point to the same endpoint, but using different Keystone versions (2 vs. 3 with domain) and that makes possible to add them as different providers. On the OSP side "default" domain with keystone v3 is the same as keystone v2 (no domains are supported), but there can be more conmplicated setups of OpenStack..

So even I understand that this might look as misleading, it is not a bug and we should not be restricting uniqueness requirements on OSP Cloud providers.
Comment 7 Marek Aufart 2018-04-17 12:01:58 UTC 
Based on Comment #6 (there are two providers and for each storage manager exists which is ok), this looks to me as not a bug, can we close it?
Comment 8 Nikhil Dhandre 2018-04-17 18:06:14 UTC 
Hi Marek,

Yes, you can close this bug. As its possible to add the same provider with different keystone version.