"incorrect object identifier" for stored objects #3805
Description
Expected Behavior
No failures.
Current Behavior
Feb 10 09:12:58 metis1 neofs-node[1094]: error replicator/process.go:87 could not replicate object {"component": "Object Replicator", "node": "02f16c467682074c3e60532f1200761bfba88c5a77d1702b4608216ec7afb02bb1", "object": "f9skWZ4YMQ4SCArgetsVTYLNGqsU6uTwxJrvwBZdfrt/29g9Gd1tMCvDY6jVhxr4iBWgJkzrAeJSdXSXfd1bPnV1", "error": "copy object using NeoFS API client of the remote node: /dns4/st2.storage.fs.neo.org/tcp/8080: status: code = 1024 message = failed to verify and store object locally: validate object format: could not validate header fields: invalid identifier: incorrect object identifier"}
...
Feb 10 09:13:26 metis1 neofs-node[1094]: error replicator/process.go:87 could not replicate object {"component": "Object Replicator", "node": "03933279423bf3504b61f76912790a566d99929eb047f30c8699f8e49a34ab07f7", "object": "mwa6Fbia757WvezeeaLfvDsA7hMhdv7bDwN34hBhc97/FubPe8VPqZmQFVodckkA6uxdVsNQaGwPFq7zZoqEAGWF", "error": "copy object using NeoFS API client of the remote node: /dns4/minerva.nspcc.ru/tcp/8080: status: code = 1024 message = failed to verify and store object locally: validate object format: could not validate header fields: invalid identifier: incorrect object identifier"}
There are others like this.
Possible Solution
Most likely some quirk is needed for old objects similar to #3359.
Steps to Reproduce (for bugs)
GET/HEAD/replicate, doesn't matter much
Context
Mainnet.
Regression
Yes. These objects are stored and should be accesible.
Your Environment
- Version used: 0.50.0