StorageGRID API for the storage usage fails by HTTP 500 "Invalid service s3 in URN"

Applies to

• StorageGRID 11.3
• S3 platform services

Issue

• StorageGRID Management API /grid/accounts/{id}/usage fails by HTTP 500 "Invalid service s3 in URN".
• The following errors can be seen in nms.log of the admin node.

ERROR   Internal server error. The server encountered an error and could not complete your request. Please try again. If the problem persists, contact Technical Support. {"Error"=>{"Code"=>"InternalError", "Message"=>"We encountered an internal error. Please try again.", "Resource"=>"/?x-ntap-sg-usage", "RequestId"=>"<REQUESTID>"}} (MgmtApi::LocalizedRuntimeError)
ERROR   /usr/local/lib/site_ruby/mgmt-api/rest-client/resource.rb:717:in `handle_errors!'
ERROR   /usr/local/lib/site_ruby/mgmt-api/accounts/account.rb:448:in `usage'
ERROR   /usr/local/mgmt-api/app/controllers/accounts.rb:259:in `block in registered'
ERROR   
        {
          "errors": [
            {
              "text": "{\"Error\"=>{\"Code\"=>\"InternalError\", \"Message\"=>\"We encountered an internal error. Please try again.\", \"Resource\"=>\"/?x-ntap-sg-usage\", \"RequestId\"=>\"<REQUESTID>\"}}",
              "key": "error.i18n.validation"
            }
          ],
          "message": {
            "text": "Internal server error. The server encountered an error and could not complete your request. Please try again. If the problem persists, contact Technical Support.",
            "key": "error.500"
          },
          "code": 500,
          "status": "error",
          "responseTime": "<TIMESTAMP>",
          "apiVersion": "2.4",
          "deprecated": true,
          "data": {
            "type": "MgmtApi::LocalizedRuntimeError",
            "trace": [
              "/usr/local/lib/site_ruby/mgmt-api/rest-client/resource.rb:717:in `handle_errors!'",
              "/usr/local/lib/site_ruby/mgmt-api/accounts/account.rb:448:in `usage'",
              "/usr/local/mgmt-api/app/controllers/accounts.rb:259:in `block in registered'",
              "/usr/lib/ruby/vendor_ruby/sinatra/base.rb:1611:in `call'",
              "/usr/lib/ruby/vendor_ruby/sinatra/base.rb:1611:in `block in compile!'",
              "/usr/lib/ruby/vendor_ruby/sinatra/base.rb:975:in `block (3 levels) in route!'",
              "/usr/lib/ruby/vendor_ruby/sinatra/base.rb:994:in `route_eval'",
              "/usr/lib/ruby/vendor_ruby/sinatra/base.rb:975:in `block (2 levels) in route!'",
              "/usr/lib/ruby/vendor_ruby/sinatra/base.rb:1015:in `block in process_route'",
              "/usr/lib/ruby/vendor_ruby/sinatra/base.rb:1013:in `catch'",
              "/usr/lib/ruby/vendor_ruby/sinatra/base.rb:1013:in `process_route'",
              "/usr/lib/ruby/vendor_ruby/sinatra/base.rb:973:in `block in route!'",
              "/usr/lib/ruby/vendor_ruby/sinatra/base.rb:972:in `each'",
              "/usr/lib/ruby/vendor_ruby/sinatra/base.rb:972:in `route!'",
              "/usr/lib/ruby/vendor_ruby/sinatra/base.rb:1085:in `block in dispatch!'"
            ]
          }
        }
 

• "Invalid service s3 in URN" is detected in bycast.log of the admin node.

ERROR    0248 S3RQ:  Unknown exception (Invalid service s3 in URN: <URN>)
NOTICE   0162 S3RQ: S3 error response: RequestId=<REQUESTID>, Resource=/?x-ntap-sg-usage,  HTTP Status Code=500, ErrorMsg=InternalError, ErrorType=Internal, CustomErrorMessage={<none>}, Details={Invalid service s3 in URN: <URN>}