1403621 - Generic worker service hitting a 401 response

Status: RESOLVED INVALID

(Infrastructure & Operations :: RelOps: General, task)

Description

[Mark Cornmesser [:markco]]

Using the same generic worker configuration file that was used in SCL3 on VMs in MDC1.

{
  "code": "AuthenticationFailed",
  "message": "Unauthorized: Stale timestamp\n----\nmethod:     claimWork\nerrorCode:  AuthenticationFailed\nstatusCode: 401\ntime:       2017-09-26T23:08:50.270Z",
  "requestInfo": {
    "method": "claimWork",
    "params": {
      "provisionerId": "scl3-puppet",
      "workerType": "gecko-t-win10-64-hw"
    },
    "payload": {
      "tasks": 1,
      "workerGroup": "scl3",
      "workerId": "T-W864-IX-000"
    },
    "time": "2017-09-26T23:08:50.270Z"
  }
}
2017/09/27 00:10:26 Could not claim work. (Permanent) HTTP response code 401
HTTP/1.1 401 Unauthorized
Content-Length: 498
Access-Control-Allow-Headers: X-Requested-With,Content-Type,Authorization,Accept,Origin
Access-Control-Allow-Methods: OPTIONS,GET,HEAD,POST,PUT,DELETE,TRACE,CONNECT
Access-Control-Allow-Origin: *
Access-Control-Request-Method: *
Connection: keep-alive
Content-Type: application/json; charset=utf-8
Date: Tue, 26 Sep 2017 23:08:55 GMT
Server: Cowboy
Strict-Transport-Security: max-age=7776000
Via: 1.1 vegur
Www-Authenticate: hawk
X-Powered-By: Express

Comment 1

[Mark Cornmesser [:markco]]

This was actually a time deviation issue. The time zone was set to UTC however it was off by +1 hour.