Bug 1384974

Summary: UI: Showing bootstrapped and non-bootstrapped 'Drop-Down' for Cloud Tenant on Add Cloud Volume page.
Product: Red Hat CloudForms Management Engine Reporter: Satyajit Bulage <sbulage>
Component: UI - OPSAssignee: Harpreet Kataria <hkataria>
Status: CLOSED DUPLICATE QA Contact: Satyajit Bulage <sbulage>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.7.0CC: ewinchel, hkataria, jhardy, mfalesni, mpovolny, obarenbo
Target Milestone: GA   
Target Release: cfme-future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: ui
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-02 03:14:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Attachments:
Description Flags
before_selecting
none
after_selecting none

Description Satyajit Bulage 2016-10-14 13:08:48 UTC
Created attachment 1210525 [details]
before_selecting

Description of problem:While adding Cloud Volume, before selecting any cloud tenant drop down seems to be a classic one. After selecting any of the cloud tenant drop down changed.(See Screenshots).


Version-Release number of selected component (if applicable):5.7.0.4-alpha1.20161005153002_cfc8a23


How reproducible:100%


Steps to Reproduce:
1.Navigate to Storage --> Volumes
2.Click on Configuration --> Add new Cloud Volume
3.

Actual results:Showing two states of drop down menu i.e. before clicking it shows classic menu and after clicking/selecting it shows bootstrapped drop down.


Expected results:It should show only bootstrapped drop down for cloud tenant.


Additional info:

Comment 2 Satyajit Bulage 2016-10-14 13:10:36 UTC
Created attachment 1210526 [details]
after_selecting

Comment 3 Eric Winchell 2016-10-24 19:45:45 UTC
*** Bug 1387168 has been marked as a duplicate of this bug. ***

Comment 5 Harpreet Kataria 2016-11-02 03:14:59 UTC

*** This bug has been marked as a duplicate of bug 1387168 ***