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 1850901

Summary:	mgr/volumes: Clone operation uses source subvolume root directory mode and uid/gid values for the clone, instead of sourcing it from the snapshot
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Kotresh HR <khiremat>
Component:	CephFS	Assignee:	Shyamsundar <srangana>
Status:	CLOSED ERRATA	QA Contact:	subhash <vpoliset>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.1	CC:	ceph-eng-bugs, pdonnell, sweil, tserlin
Target Milestone:	z2
Target Release:	4.1
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	ceph-14.2.8-100.el8cp, ceph-14.2.8-100.el7cp	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-09-30 17:26:19 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:	1863027
Bug Blocks:

Description Kotresh HR 2020-06-25 06:43:05 UTC

Description of problem:
If a subvolumes mode or uid/gid values are changed post a snapshot, and a clone of a snapshot prior to the change is initiated, the clone inherits the current source subvolumes attributes, rather than the snapshots attributes.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 8 errata-xmlrpc 2020-09-30 17:26:19 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 (Red Hat Ceph Storage 4.1 Bug Fix update), 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:4144