Bug 1319439 – When no --cloud-provider flag node providerID is "aws:///" on openstack env

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1319439 - When no --cloud-provider flag node providerID is "aws:///" on openstack env

Summary:	When no --cloud-provider flag node providerID is "aws:///" on openstack env

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Pod (Show other bugs)
Sub Component:
Version:	3.2.0
Hardware:	Unspecified Unspecified

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Andy Goldstein
QA Contact:	DeShuai Ma
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2016-03-20 00:50 EDT by DeShuai Ma
Modified:	2016-05-12 12:33 EDT (History)
CC List:	4 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2016-05-12 12:33:36 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2016:1064	normal	SHIPPED_LIVE	Important: Red Hat OpenShift Enterprise 3.2 security, bug fix, and enhancement update	2016-05-12 16:19:17 EDT

Groups: None (edit)

Description DeShuai Ma 2016-03-20 00:50:36 EDT

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

Comment 1 DeShuai Ma 2016-03-20 21:22:02 EDT

Cadvisor PR : https://github.com/google/cadvisor/pull/1171

Comment 2 Andy Goldstein 2016-03-23 09:14:10 EDT

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.

Comment 3 Troy Dawson 2016-03-23 17:24:12 EDT

This should be in OSE v3.2.0.7 that was build and pushed to qe today.

Comment 4 DeShuai Ma 2016-03-23 23:08:06 EDT

Test on openshift v3.2.0.7
the feature is revert, there is no "providerID" when there is no cloud-prover.
verify this bug.

Comment 6 errata-xmlrpc 2016-05-12 12:33:36 EDT

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

Note You need to log in before you can comment on or make changes to this bug.