Create bucket returns 400 http status code when running on SUSE OS

[bogdan-mitrea-ds]

General support information

GitHub Issues are reserved for actionable bug reports (including documentation inaccuracies), and feature requests. All questions (regarding configuration, use cases, performance, community, events, setup and usage recommendations, among other things) should be asked on the Zenko Forum.

Questions opened as GitHub issues will systematically be closed, and moved to the Zenko Forum.

---

Bug report information

Description

I am using Zenko cloudserver on and SUSE based edge device running in K3s and I am getting the 400 (InvalidURI) error when trying to create a bucket. Code hint We are using Zenko to store temporarily files on the edge device and we do not have any cloud integration.

I am running exactly the same deployment (via Kustomize) on an Anthos cluster running on Ubuntu 20.04 and there it works without any problems.

Please provide use cases for changing the current behavior

Steps to reproduce the issue

• Deploy Zenko on a K3s cluster running on a SUSE based machine (SLE 15)
• Execute a PUT request to create a bucket
• 400 Bad Request response

Actual result

The error I am getting when executing create bucket <?xml version="1.0" encoding="UTF-8"?> <Error> <Code>InvalidURI</Code> <Message>Could not parse the specified URI. Check your restEndpoints configuration.</Message> <Resource></Resource> <RequestId>cc5cfb3fec4481223987</RequestId> </Error> 2023-06-22T19:42:59.216556282Z {"name":"S3","clientIP":"::ffff:10.42.0.249","clientPort":60054,"httpMethod":"PUT","httpURL":"/storage","time":1687462979216,"req_id":"1791cc039040b279c45a","level":"info","message":"received request","hostname":"zenko-cloudserver-6cc79d8c76-v5qtr","pid":64} 2023-06-22T19:42:59.216875425Z {"name":"S3","bytesSent":233,"clientIP":"::ffff:10.42.0.249","clientPort":60054,"httpMethod":"PUT","httpURL":"/storage","httpCode":400,"time":1687462979216,"req_id":"1791cc039040b279c45a","elapsed_ms":0.283041,"level":"info","message":"responded with error XML","hostname":"zenko-cloudserver-6cc79d8c76-v5qtr","pid":64}

Expected result

I would expect the PUT request to be successful and the bucket created in Zenko cluster

Additional information

• Node.js version, v16.13.2
• Docker version, k3s version v1.27.2+k3s1 (213d7ad4)
• yarn version, yarn run v1.22.15
• distribution/OS, USE SLE15
• optional: anything else you deem helpful to us.

"port": 8000, "listenOn": [], "replicationGroupId": "RG001", "restEndpoints": { "localhost": "us-east-1", "127.0.0.1": "us-east-1", "cloudserver-front": "us-east-1", "s3.docker.test": "us-east-1", "127.0.0.2": "us-east-1", "s3.amazonaws.com": "us-east-1", "zenko-cloudserver-replicator": "us-east-1", "lb": "us-east-1", "*.edge.dscore.com": "us-east-1" },

"name": "@zenko/cloudserver", "version": "8.2.20", "description": "Zenko CloudServer, an open-source Node.js implementation of a server handling the Amazon S3 protocol", "main": "index.js", "engines": { "node": ">=16" }, "repository": "scality/S3", "keywords": [ "s3", "cloud", "server" ], "author": "Scality Inc.", "license": "Apache-2.0", "bugs": { "url": "https://github.com/scality/S3/issues" }, "homepage": "https://github.com/scality/S3#readme", "dependencies": { "@hapi/joi": "^17.1.0", "arsenal": "github:scality/Arsenal#8.1.32", "async": "~2.5.0", "aws-sdk": "2.905.0",

Feature Request

(delete this section (everything between the lines) if you're not requesting a feature but reporting a bug)

Proposal

Describe the feature

Current behavior

What currently happens

Desired behavior

What you would like to happen

Use case

Additional information

• Is this request for your company? Y/N
  • If Y: Company name:
  • Are you using any Scality Enterprise Edition products (RING, Zenko EE)? Y/N
• Are you willing to contribute this feature yourself?
• Position/Title:
• How did you hear about us?

---