Bug 1477014 - Using encryption, write and read a small file, then mess code returns
Summary: Using encryption, write and read a small file, then mess code returns
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: encryption-xlator
Version: 3.10
Hardware: x86_64
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-01 05:00 UTC by liud.fnst
Modified: 2018-06-20 18:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-20 18:24:59 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description liud.fnst 2017-08-01 05:00:58 UTC
Description of problem:
Using encryption, write and read a small file, then mess code returns

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

How reproducible:


Steps to Reproduce:
1.Created a file (file size is smaller than 1k) in the volume’s mount point.
2.Read the file, finally got a mess code.


Actual results:
no decryption is operated on the file content, so mess code returns.


Expected results:
Returns the correct data

Additional info:
I found that the content I got is from cache.
If I set the following property to off, then everything is OK.
performance.quick-read
performance.write-behind
performance.open-behind

OS : CentOS 7.1
 
Configuration
   According quick start of official website, set features.encryption to on and encryption.master-key, then start and mount the volume.

Comment 1 Shyamsundar 2018-06-20 18:24:59 UTC
This bug reported is against a version of Gluster that is no longer maintained (or has been EOL'd). See https://www.gluster.org/release-schedule/ for the versions currently maintained.

As a result this bug is being closed.

If the bug persists on a maintained version of gluster or against the mainline gluster repository, request that it be reopened and the Version field be marked appropriately.


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