Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1416107 - Can't create VM attached to VMware Standard switch
Summary: Can't create VM attached to VMware Standard switch
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - VMWare
Version: Unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-24 15:38 UTC by Perry Gagne
Modified: 2017-01-24 22:26 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-24 22:26:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Foreman debug (884.82 KB, application/x-xz)
2017-01-24 15:38 UTC, Perry Gagne 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 2700 0 None None None 2017-01-24 15:38:31 UTC

Description Perry Gagne 2017-01-24 15:38:31 UTC 
Created attachment 1243956 [details]
Foreman debug

Description of problem:
I tried to create a VM on a VMware compute resource and attach it to a network "pgagne-test-net". "pgagne-test-net" was attached to a standard switch on the host jericho.hq.gsslab.rdu.redhat.com. I wa

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


How reproducible: Everytime


Steps to Reproduce:
1. Start with a VMware enviroment with multiple hypervisors. 
2. Add the vcenter as a compute resource
3. In vmware create a standard switch and assoicated network/portgroup (ie pgagne-test-net)
4. Create a vm on the compute resource, and tie the interface of the vm to pgagne-test-net

Actual results:
Error when creating the VM:
"Failed to create a compute toldedo-vmware (VMware) instance pgagne-host1.pgagne-sat.rh-internal: failed to create vm: CannotAccessVmComponent: A component of the virtual machine is not accessible on the host."

Expected results:
VM is created on correct host. 


Additional info: Satellite has no way to specify which host a vm is created on, so there is no way i can think of to workaround this.
Comment 3 Perry Gagne 2017-01-24 22:20:39 UTC 
Chris, this is the same issue you ran into with, correct?
Comment 4 Perry Gagne 2017-01-24 22:26:33 UTC 
Hmm I tried this with a shared storage array and it seemed to work fine. I will close this for now since it appears it was a config error on my part.
Note You need to log in before you can comment on or make changes to this bug.