Scale up playbook fails to add vsphere configurations on newly added nodes to the cluster

Solution Verified - Updated -

Issue

  • While running the scale-up playbook, vSphere configurations are not being replicated on the newly added nodes within cluster.
  • vsphere.conf file is missing after running the scale-up playbook from newly added node.
  • Below error can be seen atomic-openshift-node service:
go 06 23:45:35 <Hostname> atomic-openshift-node[3788]: F0806 23:45:35.678866    3788 plugins.go:122] Couldn't open cloud provider configuration /etc/origin/cloudprovider/vsphere.conf: &os.PathError{Op:"open", Path:"/etc/origin/cloudprovider/vsphere.conf", Err:0x2}

Environment

  • Red Hat OpenShift Container Platform
    • 3.11

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content