notification log doesn't have the etag field entered correctly as compared to the put/copy object operation

[rkomandu]

Environment info

• NooBaa Version: VERSION
• Platform: Kubernetes 1.14.1 | minikube 1.1.1 | OpenShift 4.1 | other: specify

noobaa d/s build -->noobaa-core-5.18.0-20250218.el9.x86_64

Actual behavior

upload an object (using put-object) API and then the Etag is the response. In the notification log the "m" is missing, time-xxxx-ino-5vn is only present. can we fix the typo, as this is "mtime-xxxx-ino-5vn" when MD5 is disabled. 

 s3u20k1-api put-object --bucket newbucket-notify-api  --key file-3G --body /root/file_3G
urllib3/connectionpool.py:1061: InsecureRequestWarning: Unverified HTTPS request is being made to host '192.168.0.6'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/1.26.x/advanced-usage.html#ssl-warnings
{
    "ETag": "\"mtime-d7x7np2kvchs-ino-5vn\""
}


{"meta":{"connect":"notify_event.json","name":"notify_event","bucket":"newbucket-notify-api"},"notif":{"Records":[{"eventVersion":"2.3","eventSource":"rk523-13:s3","eventTime":"2025-02-20T10:45:49.499Z","s3":{"s3SchemaVersion":"1.0","object":{"sequencer":"19522f6b93b","key":"file-3G","eTag":"time-d7x7np2kvchs-ino-5v"},"bucket":{"name":"newbucket-notify-api","ownerIdentity":{"principalId":"s3user20k1"},"arn":"arn:aws:s3:::newbucket-notify-api"}},"eventName":"ObjectCreated:Put","userIdentity":{"principalId":"s3user20k1"},"requestParameters":{"sourceIPAddress":"::ffff:192.168.0.50"},"responseElements":{"x-amz-request-id":"m7d7u0xx-23lhnn-73w","x-amz-id-2":"m7d7u0xx-23lhnn-73w"}}]}}

Expected behavior

correct the typo for the notification log

Steps to reproduce

posted above

More information - Screenshots / Logs / Other output