Bug 1526496 - Unable to add VSphere to Openshift
Summary: Unable to add VSphere to Openshift
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 3.7.0
Hardware: All
OS: All
unspecified
urgent
Target Milestone: ---
: 3.7.z
Assignee: Bradley Childs
QA Contact: Jianwei Hou
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-15 16:05 UTC by Josh Foots
Modified: 2018-04-05 09:35 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-05 09:34:33 UTC
Target Upstream Version:
Embargoed:
dphillip: needinfo-

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0636 0 None None None 2018-04-05 09:35:02 UTC

Description Josh Foots 2017-12-15 16:05:52 UTC 
Description of problem:

Following [1] fails out.

[1]Configuring for VMWare vSphere | Installation and Configuration | OpenShift Container Platform 3.7
https://docs.openshift.com/container-platform/3.7/install_config/configuring_vsphere.html

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


How reproducible:

Very


Steps to Reproduce:
1. Follow the guide
2.
3.

Actual results:

Fails 

Expected results:

for it to succeed

Additional info:


Description of problem:

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

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

Master Log:

Node Log (of failed PODs):

PV Dump:

PVC Dump:

StorageClass Dump (if StorageClass used by PV/PVC):

Additional info:
Comment 1 davis phillips 2017-12-15 16:47:37 UTC 
@Josh

Can you post your vsphere.conf from /etc/origin/cloudprovider sans the vcenter password?
Comment 9 Jianwei Hou 2018-01-25 02:50:28 UTC 
vSphere installation works for me, mark as verified.
Comment 13 errata-xmlrpc 2018-04-05 09:34:33 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0636
Note You need to log in before you can comment on or make changes to this bug.