Bug 1429113 - deprecated options are automatically set on volume after snapshot restore
Summary: deprecated options are automatically set on volume after snapshot restore
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: 3.9
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Avra Sengupta
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-04 14:32 UTC by Joseph Lorenzini
Modified: 2017-03-08 12:33 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-03-08 12:33:11 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Joseph Lorenzini 2017-03-04 14:32:39 UTC
Description of problem:

If gluster snaphshot is restored, the following options are show in the volume's Options Reconfigured section

features.quota: off
features.inode-quota: off


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

3.9.0

How reproducible:


Steps to Reproduce:
1. create a gluster volume, where the bricks are LVs mounted on top of a LVM thin pool
2. use the gluster snapshot create command to create a snapshot
3. execute gluster vol info <volname> and verify that the deprecated options are not show in the reconfigured options section.
4. stop the gluster volume.
5. perform a gluster snapshot restore.
6. start the volume.
7. execute the gluster vol info <volname> command. Note the deprecated options reappear.
8. Attempt to reset fail with:

gluster vol reset gv0 features.inode-quota force
volume reset: failed: 'gluster volume reset <VOLNAME> features.inode-quota' is deprecated. Use 'gluster volume quota <VOLNAME> disable' instead.

Actual results:

A deprecated option is added to my volume after a snapshot restore

Expected results:

After a snapshot restore, no additional options should be set on the volume.

Comment 1 Kaushal 2017-03-08 12:33:11 UTC
This bug is getting closed because GlusterFS-3.9 has reached its end-of-life [1].

Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please open a new bug against the newer release.

[1]: https://www.gluster.org/community/release-schedule/


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