Negative scenario. s3 gateway closed connection without right answer to client while we set versioning state of bucket with wrong value #315

New issue

Closed

opened 2025-12-28 17:36:58 +00:00 by sami · 0 comments

sami commented

2025-12-28 17:36:58 +00:00

Owner

Originally created by @anikeev-yadro on GitHub (Aug 22, 2022).

Originally assigned to: @KirillovDenis on GitHub.

I tried to set versioning state with wrong value of parameter Status:
aws --no-verify-ssl s3api put-bucket-versioning --bucket b-test-lock-6 --endpoint-url http://172.26.163.38:8084 --versioning-configuration Status=Disabled
But instead of answer with error, s3 gateway closed connection:
Connection was closed before we received a valid response from endpoint URL: "http://172.26.163.38:8084/b-test-lock-6?versioning".

Log: bucket_vesions_bug.log

Product versions:

s3 gateway
Version: v0.23.0-36-g3b343d1-dirty
GoVersion: go1.18.4

NeoFS Storage node
Version: v0.31.0
GoVersion: go1.18.4

NeoGo
Version: 0.99.1
GoVersion: go1.18.4

s3 gateway config:

listen_address: 0.0.0.0:8084
logger:
  level: debug
max_clients_count: 600
max_clients_deadline: 60s
peers:
  '0':
    address: node1.neofs:8080
    priority: '1'
    weight: '1'
  '1':
    address: node2.neofs:8080
    priority: '2'
    weight: '0.25'
  '2':
    address: node3.neofs:8080
    priority: '2'
    weight: '0.25'
  '3':
    address: node4.neofs:8080
    priority: '2'
    weight: '0.25'
pool_error_threshold: 100
pprof:
  address: localhost:8085
  enabled: true
prometheus:
  address: localhost:8086
  enabled: true
resolve_order:
- nns
rpc_endpoint: http://node1.neofs:40332
tree:
  service: 172.26.163.38:8080
wallet:
  address: ''
  passphrase: ''
  path: /etc/neofs/s3/wallet.json

Originally created by @anikeev-yadro on GitHub (Aug 22, 2022). Originally assigned to: @KirillovDenis on GitHub. I tried to set versioning state with wrong value of parameter Status: `aws --no-verify-ssl s3api put-bucket-versioning --bucket b-test-lock-6 --endpoint-url http://172.26.163.38:8084 --versioning-configuration Status=Disabled` But instead of answer with error, s3 gateway closed connection: `Connection was closed before we received a valid response from endpoint URL: "http://172.26.163.38:8084/b-test-lock-6?versioning".` **Log:** [bucket_vesions_bug.log](https://github.com/nspcc-dev/neofs-s3-gw/files/9392555/bucket_vesions_bug.log) **Product versions:** ``` s3 gateway Version: v0.23.0-36-g3b343d1-dirty GoVersion: go1.18.4 NeoFS Storage node Version: v0.31.0 GoVersion: go1.18.4 NeoGo Version: 0.99.1 GoVersion: go1.18.4 ``` **s3 gateway config:** ```default_policy: REP 1 IN X CBF 1 SELECT 1 FROM * AS X listen_address: 0.0.0.0:8084 logger: level: debug max_clients_count: 600 max_clients_deadline: 60s peers: '0': address: node1.neofs:8080 priority: '1' weight: '1' '1': address: node2.neofs:8080 priority: '2' weight: '0.25' '2': address: node3.neofs:8080 priority: '2' weight: '0.25' '3': address: node4.neofs:8080 priority: '2' weight: '0.25' pool_error_threshold: 100 pprof: address: localhost:8085 enabled: true prometheus: address: localhost:8086 enabled: true resolve_order: - nns rpc_endpoint: http://node1.neofs:40332 tree: service: 172.26.163.38:8080 wallet: address: '' passphrase: '' path: /etc/neofs/s3/wallet.json ```