Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1639724

Summary:	Flag RBD_FLAG_FAST_DIFF_INVALID is not exposed in Python bindings
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Ernesto Puerta <epuertat>
Component:	RBD	Assignee:	Jason Dillaman <jdillama>
Status:	CLOSED ERRATA	QA Contact:	Tejas <tchandra>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	3.2	CC:	ceph-eng-bugs, kdreyer, rperiyas, tchandra, tserlin
Target Milestone:	z1	Keywords:	CodeChange
Target Release:	3.2
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	RHEL: ceph-12.2.8-70.el7cp Ubuntu: ceph_12.2.8-55redhat1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-07 15:50:56 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:	1639716

Description Ernesto Puerta 2018-10-16 13:01:07 UTC

Description of problem:
While flag rbd.RBD_FLAG_FAST_DIFF_INVALID exists in Luminous, it's not exposed in the Python bindings. It was fixed in Mimic, together with additions of new flags, in commit 36d3b17dc8c9af0d62ada4b9b0e4af58ec825b46.

The fix is trivial and has been already done for Ceph-dashboard backporting: https://github.com/rhcs-dashboard/ceph/commit/36656fa

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

How reproducible:
From command line interface.

Steps to Reproduce:
In CLI run: python -c 'from rbd import RBD_FLAG_FAST_DIFF_INVALID'

Actual results:
Error printed: "ImportError: cannot import name RBD_FLAG_FAST_DIFF_INVALID"

Expected results:
No error shown.

Additional info:
NA

Comment 14 errata-xmlrpc 2019-03-07 15:50:56 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:0475