Bug 1389032

Summary:	vSphere plugin causing panic
Product:	OpenShift Container Platform	Reporter:	Erin Boyd <eboyd>
Component:	Storage	Assignee:	Erin Boyd <eboyd>
Status:	CLOSED WONTFIX	QA Contact:	Jianwei Hou <jhou>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.4.0	CC:	aos-bugs, bchilds, eparis, jhou
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-28 17:58:42 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 Erin Boyd 2016-10-26 17:19:20 UTC

Description of problem:

Improper configuration of vSphere causing panic

Version-Release number of selected component (if applicable):
Kube 1.4.4 and below

How reproducible:
Always

Steps to Reproduce:
1.Deploy OCP 3.4 on vSphere
2.Configure Storage Class with vSphere provisioner
3.Create pvc to request Storage class

Actual results:
Master node fails with panic

Expected results:


Additional info:

Bug is fixed in these:
https://github.com/kubernetes/kubernetes/pulls?utf8=%E2%9C%93&q=%20is%3Apr%20author%3Akerneltime%20

Comment 1 Eric Paris 2016-10-27 19:31:50 UTC

https://github.com/openshift/origin/11598

Comment 2 Bradley Childs 2016-10-28 16:26:23 UTC

(In reply to Eric Paris from comment #1)
> https://github.com/openshift/origin/11598
bad link

good link
https://github.com/openshift/origin/pull/11598

Comment 4 Erin Boyd 2016-11-04 17:55:18 UTC

*** Bug 1391863 has been marked as a duplicate of this bug. ***

Comment 5 Erin Boyd 2016-11-07 21:32:06 UTC

another panic:

2016-11-07 19:41:06.047705 I | etcdserver/api/v3rpc: grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp 10.19.114.240:4001: getsockopt: connection refused"; Reconnecting to {10.19.114.240:4001 <nil>}
panic: reflect.Set: value of type mo.ResourcePool is not assignable to type mo.ComputeResource

https://github.com/kubernetes/kubernetes/issues/36295

Comment 6 Erin Boyd 2016-11-07 21:32:54 UTC

Per Mike Barret --- we are moving support for vsphere in 3.4 out thus removing 'blocker'

Comment 7 Eric Paris 2017-01-28 17:58:42 UTC

vSphere is unsupported. We will get improvements in 3.5 from upstream but we are not going to actively work this BZ.