Get object in namespaced s3 compatible bucket only returns first 4kiB

Environment info

• NooBaa Version: master+74b79637d8a9a1dca2baf51598860579711a5c6b
• Platform: OKD 4.5

Actual behavior

1. Performing a GET to any object in a namespaced bucket returns only the first 4kiB.

Expected behavior

1. Performing a GET to any object in a namespaced bucket should return the full object

Steps to reproduce

1. Create namespaced s3 compatible bucket
2. Upload an object
3. GET the object

More information - Screenshots / Logs / Other output

Also the metadata of all objects is reported incorrectly, as Content-Length Noobaa always states 4096.

As far as i can see this commit from @paulxuzhang introduced the problem here: https://github.com/noobaa/noobaa-core/blob/72a0fbc92ac4c29a98a8ab3eca3118a167860f5b/src/sdk/namespace_s3.js#L142-L144

Also i noticed that even when you send a headObject request to Noobaa this function (read_object_md) gets called and performs a getObject, instead of only calling headObject on the backend.

[paulxuzhang]

@guymguym Created PR https://github.com/noobaa/noobaa-core/pull/6167 for this issue. The root cause is that the changes supporting partNumber query parameter sets content-length to the one returned by hub, it ends up that content-length is set to Inline Range Length (4kb) for object with size > 4kb if partNumber query parameter is NOT set.

We should whether we have existing tests or create new for validating that.

[guymguym]

Fixed by #6167