Bug 1327601

Summary: UI: 'Network Adaptor Information' vlan* shows '<No Choices Available>' for vSphere55 provisioned VM
Product: Red Hat CloudForms Management Engine Reporter: Satyajit Bulage <sbulage>
Component: UI - OPSAssignee: Brandon Dunne <bdunne>
Status: CLOSED WORKSFORME QA Contact: Satyajit Bulage <sbulage>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 5.6.0CC: cpelland, gmccullo, hkataria, jhardy, mpovolny, obarenbo, sbulage
Target Milestone: GA   
Target Release: 5.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: ui:provision
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-26 20:48:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Satyajit Bulage 2016-04-15 13:09:21 UTC 
Description of problem: While provisioning vm from vSphere55 provider Network Adapter Information vlan* drop down menu shows '<No Choices Available>'.


Version-Release number of selected component (if applicable): 5.6.0.1-beta2.20160413141124_e25ac0e


How reproducible: 100%


Steps to Reproduce:
1.After adding vSphere55 provider 
2.Navigate to Infrastructure --> Virtual Machines --> Life Cycle--> Provision VM
3.Enter all required values and Navigate to Network tab on Provision Virtual Machines.
4.Try to select vLan under Network Adapter Information


Actual results: After clicking on drop down menu of vLan, itshows '<No Choices Availble>'


Expected results: After clicking on drop down menu of vLan should show available networks.


Additional info:
Comment 2 Greg McCullough 2016-04-15 16:17:26 UTC 
Satyajit - Can you validate if this is the same issue as Bug 1327217?

If you are not seeing host/storage populated on the Environment tab vlans will not work as well.

My guess is that it is the same and this can be closed as a duplicate.
Comment 3 Brandon Dunne 2016-04-26 20:48:10 UTC 
This appears to be the same issue as 1327217.  If it is not, please reopen with more details on how to reproduce this problem.