Bug 1427701

Summary:	node repeatedly tries to attach an already attached OpenStack Cinder volume for use as a PV/PVC
Product:	OpenShift Container Platform	Reporter:	Eric Jones <erjones>
Component:	Storage	Assignee:	hchen
Status:	CLOSED ERRATA	QA Contact:	Jianwei Hou <jhou>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.3.1	CC:	aos-bugs, bchilds, eparis, erich, erjones, geguileo, hchen, rhowe, smunilla
Target Milestone:	---	Keywords:	Unconfirmed
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	Feature: Support OpenStack V2 API Reason: OpenStack Cinder v1 API is deprecated in recent OpenStack release. Result: This fix supports OpenStack V2 API.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-10 05:18:47 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:
Embargoed:

Description Eric Jones 2017-02-28 22:20:02 UTC

Description of problem:
Using OpenStack as the cloud-provider and the storage provider the customer is able to check the node logs and see messages of the cluster trying (and failing) to attach a single volume over and over, despite the first time it tried, it succeeded.

Version-Release number of selected component (if applicable):
[root@openshift-master-1 ~]# openshift version
openshift v3.3.1.7
kubernetes v1.3.0+52492b4
etcd 2.3.0+git

OpenStack version is Kilo.


Additional info:
Attaching node logs and Openstack cinder-api logs shortly

Comment 8 Eric Rich 2017-03-01 18:26:02 UTC

OSP 8 seems to have deprecated these API's https://access.redhat.com/solutions/2567901

Comment 38 Jianwei Hou 2017-05-31 09:08:52 UTC

The issue is not reproduced on v3.6.86, mark as verified.

Comment 40 errata-xmlrpc 2017-08-10 05:18:47 UTC

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/RHEA-2017:1716