Bug 1391863

Summary: vSphere cloud provider did not initialize properly
Product: OpenShift Container Platform Reporter: Jianwei Hou <jhou>
Component: NodeAssignee: Derek Carr <decarr>
Status: CLOSED DUPLICATE QA Contact: DeShuai Ma <dma>
Severity: medium Docs Contact:
Priority: high    
Version: 3.4.0CC: aos-bugs, eboyd, jokerman, mmccomas
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: 2016-11-04 17:55:18 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 Jianwei Hou 2016-11-04 09:26:05 UTC
Description of problem:
Setup OCP 3.4 on vsphere, create a cloud.conf with vsphere credentials, enable vsphere cloud provider in node config. After node is restarted, got error "Cloud provider not initialized properly", but there is no clear clue why it was not properly initialized.

Version-Release number of selected component (if applicable):
openshift v3.4.0.21+ca4702d
kubernetes v1.4.0+776c994
etcd 3.1.0-rc.0

How reproducible:
Always

Steps to Reproduce:
1. Install latest ocp with openshift-ansible
2. created /etc/cloud.conf with:
[Global]
        user = [hidden]
        password = [hidden]
        server = [hidden]
        port = 443
        insecure-flag = 1
        datacenter = Datacenter
        datastore = datastore1

[Disk]
        scsicontrollertype = pvscsi


In master-config.yaml set:
  apiServerArguments:
    cloud-provider:
    - "vsphere"
    cloud-config:
    - "/etc/cloud.conf"
  controllerArguments:
    cloud-provider:
    - "vsphere"
    cloud-config:
    - "/etc/cloud.conf"
Then restart master

In node-config.yaml set:
kubeletArguments:
  cloud-provider:
    - "vsphere"
  cloud-config:
    - "/etc/cloud.conf"
Then restart node

Actual results:
Node is restarted successfully but did not become 'Ready', run 'journalctl' and error "Cloud provider not initialized properly" is shown.

Expected results:
Should have cloud provider initialized successfully

Additional info:
Using same cloud.conf in Kubernetes, cloud provider is initialized properly. Not sure what needs to be tuned in ocp

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

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