eACL wrong behavior with user headers filters: STRING_NOT_EQUAL and STRING_EQUAL (complex obj) #687

New issue

Open

opened 2023-09-13 09:25:52 +00:00 by anikeev-yadro · 1 comment

anikeev-yadro commented

2023-09-13 09:25:52 +00:00

Member

Related #676

Autotest name

testsuites.acl.test_eacl_filters.TestEACLFilters#test_extended_acl_allow_filters_object

Expected Behavior

eACL should allow PUT operations with user headers filters: STRING_NOT_EQUAL and STRING_EQUAL

Current Behavior

eACL doesn't allow PUT operations with user headers filters: STRING_NOT_EQUAL and STRING_EQUAL.

Steps to Reproduce (for bugs)

Create container
PUT object
Deny all operations for others except few operations allowed by object filter
Check other can get objects with attributes matching the filter
Cannot PUT complex object

COMMAND: frostfs-cli --config /jenkins/workspace/sbercloud_functional_tests_nightly/tmp.PKLhbLFGJk/frostfs-testcases/wallet_config.yml object put --rpc-endpoint '172.26.161.215:8080' --wallet '/jenkins/workspace/sbercloud_functional_tests_nightly/tmp.PKLhbLFGJk/frostfs-testcases/TemporaryDir/0bdb166b-c342-457b-96d0-bf82f1ede3ac.json' --cid 'ArKCFHrdBRJoztAvV36EGCQiMYp8EU7wk9gHQjgs7g8L' --file 'TemporaryDir/ed1c0e7c-3946-4d1f-86eb-410c9f2142b7' --attributes 'check_key=check_value' --no-progress
RETCODE: 1

STDOUT:
rpc error: client failure: status: code = 1024 message = incomplete object PUT by placement: could not write header: (*putsvc.remoteTarget) could not put single object to [/ip4/172.26.162.160/tcp/8080]: put single object via client: status: code = 2048 message = access to object operation denied

STDERR:

Start / End / Elapsed	 00:41:51.745487 / 00:41:54.139186 / 0:00:02.393699

Regression

Yes

Version

0.0.1-897-gaa9f8dce

Your Environment

Virtual
4 nodes

Related https://git.frostfs.info/TrueCloudLab/frostfs-node/issues/676 ## Autotest name testsuites.acl.test_eacl_filters.TestEACLFilters#test_extended_acl_allow_filters_object ## Expected Behavior eACL should allow PUT operations with user headers filters: STRING_NOT_EQUAL and STRING_EQUAL ## Current Behavior eACL doesn't allow PUT operations with user headers filters: STRING_NOT_EQUAL and STRING_EQUAL. ## Steps to Reproduce (for bugs) 1. Create container 2. PUT object 3. Deny all operations for others except few operations allowed by object filter 4. Check other can get objects with attributes matching the filter 5. Cannot PUT complex object ``` COMMAND: frostfs-cli --config /jenkins/workspace/sbercloud_functional_tests_nightly/tmp.PKLhbLFGJk/frostfs-testcases/wallet_config.yml object put --rpc-endpoint '172.26.161.215:8080' --wallet '/jenkins/workspace/sbercloud_functional_tests_nightly/tmp.PKLhbLFGJk/frostfs-testcases/TemporaryDir/0bdb166b-c342-457b-96d0-bf82f1ede3ac.json' --cid 'ArKCFHrdBRJoztAvV36EGCQiMYp8EU7wk9gHQjgs7g8L' --file 'TemporaryDir/ed1c0e7c-3946-4d1f-86eb-410c9f2142b7' --attributes 'check_key=check_value' --no-progress RETCODE: 1 STDOUT: rpc error: client failure: status: code = 1024 message = incomplete object PUT by placement: could not write header: (*putsvc.remoteTarget) could not put single object to [/ip4/172.26.162.160/tcp/8080]: put single object via client: status: code = 2048 message = access to object operation denied STDERR: Start / End / Elapsed 00:41:51.745487 / 00:41:54.139186 / 0:00:02.393699 ``` ## Regression Yes ## Version ``` 0.0.1-897-gaa9f8dce ``` ## Your Environment Virtual 4 nodes