Bug #46163
closed
mgr/volumes: Clone operation uses source subvolume root directory mode and uid/gid values for the clone, instead of sourcing it from the snapshot
Added by Shyamsundar Ranganathan almost 4 years ago.
Updated over 3 years ago.
Category:
Correctness/Safety
Backport:
octopus,nautilus
Component(FS):
mgr/volumes
Description
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.
- Status changed from New to Triaged
- Assignee set to Kotresh Hiremath Ravishankar
- Target version set to v16.0.0
- Assignee changed from Kotresh Hiremath Ravishankar to Shyamsundar Ranganathan
- Status changed from Triaged to Fix Under Review
- Pull request ID set to 35756
- Status changed from Fix Under Review to In Progress
- Status changed from In Progress to Fix Under Review
- Status changed from Fix Under Review to Pending Backport
- Copied to Backport #47058: nautilus: mgr/volumes: Clone operation uses source subvolume root directory mode and uid/gid values for the clone, instead of sourcing it from the snapshot added
- Copied to Backport #47059: octopus: mgr/volumes: Clone operation uses source subvolume root directory mode and uid/gid values for the clone, instead of sourcing it from the snapshot added
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Also available in: Atom
PDF