Bug 1838959 - mgr/volumes: Not able to resize cephfs subvolume with ceph fs subvolume create command
Summary: mgr/volumes: Not able to resize cephfs subvolume with ceph fs subvolume creat...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: CephFS
Version: 4.1
Hardware: All
OS: All
medium
medium
Target Milestone: z1
: 4.1
Assignee: Kotresh HR
QA Contact: subhash
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-22 07:24 UTC by Kotresh HR
Modified: 2020-07-20 14:21 UTC (History)
6 users (show)

Fixed In Version: ceph-14.2.8-66.el8cp, ceph-14.2.8-68.el7cp
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-20 14:21:24 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 45681 0 None None None 2020-06-11 16:09:25 UTC
Red Hat Product Errata RHSA-2020:3003 0 None None None 2020-07-20 14:21:41 UTC

Description Kotresh HR 2020-05-22 07:24:15 UTC
Description of problem:
Earlier, cephfs subvolume resize could be done using subvolume create command. This is no longer working after introducing subvolume clone. Please check the upstream tracker attached for more information.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 RHEL Program Management 2020-05-22 07:24:23 UTC
Please specify the severity of this bug. Severity is defined here:
https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity.

Comment 8 errata-xmlrpc 2020-07-20 14:21: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/RHSA-2020:3003


Note You need to log in before you can comment on or make changes to this bug.