Bug 1579247

Summary: [RFE] make ceph_volume_client library python3 compatible
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Ram Raja <rraja>
Component: CephFSAssignee: Rishabh Dave <ridave>
Status: CLOSED ERRATA QA Contact: Ramakrishnan Periyasamy <rperiyas>
Severity: low Docs Contact:
Priority: high    
Version: 3.0CC: ceph-eng-bugs, ceph-qe-bugs, hnallurv, kdreyer, pdonnell, ridave
Target Milestone: rcKeywords: FutureFeature
Target Release: 3.2   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: RHEL: ceph-12.2.8-12.el7cp Ubuntu: ceph_12.2.8-10redhat1 Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-03 19:01:22 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:
Bug Depends On:    
Bug Blocks: 1553198    

Description Ram Raja 2018-05-17 09:03:48 UTC
Description of problem:
The ceph_volume_client python library used by OpenStack Manila is not py3 compliant. It needs to be py3 compliant in time for OSP 14 release, in which Manila's CephFS drivers would use ceph_volume_client library in py2 and py3 environments. 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 11 Ramakrishnan Periyasamy 2018-11-23 11:19:38 UTC
Hi  Rishabh, 
We are not having python3 environment in downstream teuthology, Did we tested this in upstream teuthology with python3 env ? and if tests all passed in upstream, we would like to close this bz as SanityOnly. Let us know your comments.

Comment 12 Patrick Donnelly 2018-11-26 23:31:04 UTC
We've tested this in upstream regularly. We can close this SanityOnly IMO.

Comment 14 Ramakrishnan Periyasamy 2018-11-28 06:17:10 UTC
Thanks Patrick for the suggestion.

Moving this bug to verified state as SanityOnly as per comment 11 & 12.

Comment 16 errata-xmlrpc 2019-01-03 19:01:22 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/RHBA-2019:0020