Bug 1238850 - setxattr does not fail with incorrect prefix
Summary: setxattr does not fail with incorrect prefix
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: GlusterFS
Classification: Community
Component: libgfapi-python
Version: mainline
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-02 19:50 UTC by Alex Campbell
Modified: 2018-10-12 07:10 UTC (History)
3 users (show)

Fixed In Version: glusterfs-4.1.4
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-12 07:10:05 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Alex Campbell 2015-07-02 19:50:05 UTC
Description of problem:

When attempting to use setxattr without a proper prefix (user, system, trusted, security), or no prefix,  it does not return an error.

Steps to reproduce:

with improper prefix:

$ python
>> vol = gfapi.Volume(<some server>,<some volume>)
>> vol.mount()
>> vol.setxattr('/tmp/test', 'a.test', 'value')

OR

with no prefix:

$ python
>> vol = gfapi.Volume(<some server>,<some volume>)
>> vol.mount()
>> vol.setxattr('/tmp/test', 'test', 'value')


Expected results:

Should throw proper error.

Comment 3 Kaleb KEITHLEY 2015-10-22 17:00:12 UTC
changing version to mainline in order to retire pre-release.

If you know the appropriate, correct version for this bug, please
set it.

Comment 4 Kaleb KEITHLEY 2015-10-22 17:06:51 UTC
changing version to mainline in order to retire pre-release.

If you know the appropriate, correct version for this bug, please
set it.

Comment 5 Kaleb KEITHLEY 2015-10-22 17:11:18 UTC
changing version to mainline in order to retire pre-release.

If you know the appropriate, correct version for this bug, please
set it.

Comment 6 Amar Tumballi 2018-10-12 07:10:05 UTC
Not sure when its fixed, but it gives the expected error when ran with gfapi APIs.


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