Bug 1717940

Summary: py3 librados get_fsid() function returns bytes instead of a string
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Lee Yarwood <lyarwood>
Component: RADOSAssignee: Jason Dillaman <jdillama>
Status: CLOSED ERRATA QA Contact: Yogev Rabl <yrabl>
Severity: high Docs Contact:
Priority: high    
Version: 4.0CC: anharris, ceph-eng-bugs, ceph-qe-bugs, dzafman, gfidente, gmeno, jdillama, jdurgin, johfulto, kchai, kdreyer, lhh, mmurthy, nojha, tchandra, tserlin
Target Milestone: rc   
Target Release: 4.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ceph-14.2.1-508.g0f9d32b.el8cp Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-01-31 12:46:18 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: 1594251    

Description Lee Yarwood 2019-06-06 13:49:53 UTC
Description of problem:
This has been reported against openstack/cinder upstream in the following bug:

Acceleration cinder - glance with ceph not working
https://bugs.launchpad.net/cinder/+bug/1816468

With a workaround landing recently for this:

Fix python3 compatibility of rbd get_fsid
https://review.opendev.org/#/c/635195/

This was also fixed in ceph itself and backported to some older releases but doesn't appear present in the bits used by OSP 15:

https://github.com/ceph/ceph/pull/27259
http://tracker.ceph.com/issues/38872

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

How reproducible:
Always

Steps to Reproduce:
1. call get_fsid

Actual results:
bytes returned.

Expected results:
string returned.

Additional info:

Comment 14 Giridhar Ramaraju 2019-08-05 13:09:10 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 15 Giridhar Ramaraju 2019-08-05 13:10:30 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 19 errata-xmlrpc 2020-01-31 12:46:18 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-2020:0312