Description of problem: When no --cloud-provider flag is given, The node providerID is "aws:///xxx" on openstack env. On gce/aws env get providerID correctly Version-Release number of selected component (if applicable): openshift v3.2.0.5 kubernetes v1.2.0-36-g4a3f9c5 etcd 2.2.5 atomic-openshift-3.2.0.5-1.git.0.f1bac72.el7.x86_64 How reproducible: Always Steps to Reproduce: 1.Setup a multi node env on openstack 2.Check node info [root@openshift-116 ~]# oc get node NAME STATUS AGE openshift-110.lab.sjc.redhat.com Ready 3h openshift-116.lab.sjc.redhat.com Ready 37m [root@openshift-116 ~]# oc get node openshift-110.lab.sjc.redhat.com -o json|grep providerID "providerID": "aws:////i-00001167" [root@openshift-116 ~]# oc get node openshift-116.lab.sjc.redhat.com -o json|grep providerID "providerID": "aws:////i-00001166" Actual results: 2.Node info should be "openstack:////xxxx" Expected results: Additional info: related pr: https://github.com/openshift/origin/pull/8062
Cadvisor PR : https://github.com/google/cadvisor/pull/1171
The fix has merged to origin: https://github.com/openshift/origin/pull/8197. This backs out a previous upstream PR that resulted in this bug.
This should be in OSE v3.2.0.7 that was build and pushed to qe today.
Test on openshift v3.2.0.7 the feature is revert, there is no "providerID" when there is no cloud-prover. verify this bug.
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/RHSA-2016:1064