Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1238850

Summary: setxattr does not fail with incorrect prefix
Product: [Community] GlusterFS Reporter: Alex Campbell <acampbel>
Component: libgfapi-pythonAssignee: bugs <bugs>
Status: CLOSED WORKSFORME QA Contact:
Severity: low Docs Contact:
Priority: unspecified    
Version: mainlineCC: atumball, bugs, rwheeler
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-4.1.4 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-12 07:10:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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.