The record lifetime is calculated using the block reception time

[dansingjulia]

I cannot create container with s3 creads by 30sec. The problem occurs due to untimely invalidation of a negative response in the storage node cache. We need to tweak the lifetime of the record. It should not exceed the block reception time.

Steps:

The initialization step of S3 creds breaks. It falls off by timeout:

03:33:21 [INFO] Executing command: neofs-authmate --debug --with-log --timeout 30s issue-secret --wallet /tests/TemporaryDir/279819cb-bc34-4627-8088-dfe4c13e0d4a.json --gate-public-key=027b5891f38c1d2c7933694c93d62512f6e90acd435e6a4d88dd18ca13a65c665b --peer 172.26.163.163:8080 --container-friendly-name 19fe35a2-6dea-41fd-b591-0fa601112d49 --bearer-rules /tests/robot/resources/files/s3_bearer_rules.json
03:33:52 [INFO] Command completed with output: Enter password for /tests/TemporaryDir/279819cb-bc34-4627-8088-dfe4c13e0d4a.json > 
2022-09-27T03:33:22.514Z	DEBUG	s3-authmate/main.go:595	prepare connection pool
2022-09-27T03:33:22.525Z	INFO	authmate/authmate.go:236	check container or create	{"cid": "11111111111111111111111111111111", "friendly_name": "19fe35a2-6dea-41fd-b591-0fa601112d49", "placement_policy": "REP 2 IN X CBF 3 SELECT 2 FROM * AS X"}
failed to issue secret: check container: create container in NeoFS: save container via connection pool: wait container presence on client: context deadline exceeded

Expected Behavior

Container created successfully

Current Behavior

Run timeout error

Expected Solution

Need to tweak the lifetime of the record. It should not exceed the block reception time.
/neofs/storage/config.yml:

morph:
  cache_ttl: 15s

config/protocol.mainnet.yml

  SecondsPerBlock: 15