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 1600068

Summary:	ceph_volume_client: allow atomic updates of object
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Ram Raja <rraja>
Component:	CephFS	Assignee:	Rishabh Dave <ridave>
Status:	CLOSED ERRATA	QA Contact:	Ramakrishnan Periyasamy <rperiyas>
Severity:	low	Docs Contact:
Priority:	high
Version:	3.0	CC:	ceph-eng-bugs, ceph-qe-bugs, hnallurv, kdreyer, pdonnell, vakulkar
Target Milestone:	rc
Target Release:	3.2
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	RHEL: ceph-12.2.8-13.el7cp Ubuntu: ceph_12.2.8-10redhat1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-01-03 19:01:24 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 Ram Raja 2018-07-11 11:03:07 UTC

Description of problem:
Need to expose APIs to enable manila's cephfs driver to atomically update RADOS objects. Implement 'put_object_versioned()' and 'get_object_and_version()' methods in ceph_volume_client to allow the manila driver to do so.

You can run the following test in the qa suite to verify that the new method work,
https://github.com/ceph/ceph/pull/22455/commits/8ab6f84d5799cf2f32fb2b08168ff1cfb82f7d15#diff-56d08f4280046bb7c3fad415cbc9e425R973

Comment 8 Vasu Kulkarni 2018-11-21 18:55:02 UTC

Verified in following fs regression run: http://pulpito.ceph.redhat.com/vasu-2018-11-17_00:06:38-fs-luminous-distro-basic-argo/

specific test: http://pulpito.ceph.redhat.com/vasu-2018-11-17_00:06:38-fs-luminous-distro-basic-argo/313866/

Comment 9 Ramakrishnan Periyasamy 2018-11-22 03:57:01 UTC

Moving the bug to verified state.

Comment 11 errata-xmlrpc 2019-01-03 19:01:24 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