eACL wrong behavior with user headers filters: STRING_NOT_EQUAL and STRING_EQUAL. #676
Labels
No labels
P0
P1
P2
P3
badger
frostfs-adm
frostfs-cli
frostfs-ir
frostfs-lens
frostfs-node
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#676
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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)
Regression
Yes
Version
Your Environment
Virtual
4 nodes
Hm, this may be related to object size, let's check both small and big objects.
@fyrchik
We caught this bug with simple object.
Do you want to retest with complex object?
No, we will try both on dev-env anyway.
OK. Anyway we will expand our ACL tests with complex objects.