You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TestNet nodes couldn't replicate following object from public container:
`error replicator/process.go:62 could not replicate object {"component": "Object Replicator", "node": "03000a222431891c481f2fbce61297547e816e164750f5ea94e2831c219bbe3504", "object": "GqNR1XtkucMcxE86FtALjVUSFVREa9ZMF2fbmeXEffJV/JDbZcmiZWCXRocjHU6i9ZHqJZzTDrhk2HEET33vxJJ6s", "error": "(*putsvc.RemoteSender) could not send object: (*putsvc.remoteTarget) could not put object to [/dns4/st4.t5.fs.neo.org/tcp/8080]: write object via client: status: code = 1024 message = (*object.FormatValidator) different owner identifiers NfFA5g92e32YvraVmipA9oY8AjvbdgFdjY/NTBbJxp2PrPXS7XyhKVqroifvsp1QCttif"}`
Both correspond to NfFA5g92e32YvraVmipA9oY8AjvbdgFdjY address. A container owner signed a token for himself, it's attached to the object, but the key that signed the object is different (not a part of a token, nor a container owner key). When I was looking at #2226 I had an impression that the object is in fact signed by the same (NfFA5g92e32YvraVmipA9oY8AjvbdgFdjY in out case) key, but it's different. If we have it in the store this likely means that it can be created because of basic/extended ACL rules that allow this to happen, right? Which then means that it should be able to replicate.
TestNet nodes couldn't replicate following object from public container:
Object header
The text was updated successfully, but these errors were encountered: