Bug 1381875 - WebUI: Cloud Tenant drop box display issue
Summary: WebUI: Cloud Tenant drop box display issue
Keywords:
Status: CLOSED DUPLICATE of bug 1387168
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: GA
: cfme-future
Assignee: Eric Winchell
QA Contact: Ramesh A
URL:
Whiteboard: ui:cloud:volume:tenant_cfme
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-05 09:01 UTC by Ramesh A
Modified: 2016-11-18 14:42 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-18 14:42:39 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
rananda: automate_bug-

Attachments (Terms of Use)
before (57.66 KB, image/jpeg)
2016-10-05 09:01 UTC, Ramesh A 		no flags Details
after (55.72 KB, image/jpeg)
2016-10-05 09:01 UTC, Ramesh A 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Ramesh A 2016-10-05 09:01:02 UTC 
Created attachment 1207499 [details]
before

Description of problem:
Cloud Tenant drop box display issue

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

How reproducible:
Very

Steps to Reproduce:
1. Navigate to Compute ==> Clouds ==> Volumes ==> Configuration ==> Add a new Cloud Volume.
2. Observe the "Cloud Tenant" drop down.

Actual results:
Cloud Tenant drop down box is not compliant with the other drop drown boxes.  Refer the screenshot "before" and "after" for further information

PS:
Now change the drop down value to say admin and observe the change in the drop down box display

Expected results:
Drop down box should be compliant to the rest of the drop downs across the appliance

Additional info:
Comment 2 Ramesh A 2016-10-05 09:01:33 UTC 
Created attachment 1207500 [details]
after
Comment 6 Eric Winchell 2016-11-18 14:42:39 UTC 

*** This bug has been marked as a duplicate of bug 1387168 ***
Note You need to log in before you can comment on or make changes to this bug.