Project

General

Profile

Actions

Bug #17353

closed

[deployment] Misleading WARNING messages on arvados-api-server install?

Added by Javier Bértoli about 3 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
Deployment
Target version:
Story points:
-
Release relationship:
Auto

Description

When doing a fresh install, I see these WARNING messages in the output

Setting up database...ESC[33mWARNESC[0m[2021-02-09T11:02:21.924396390Z] Clusters.xxxxx.ManagementToken: secret token is not set (use 32+ random characters from a-z, A-Z, 0-9) 
ESC[33mWARNESC[0m[2021-02-09T11:02:21.924472002Z] Clusters.xxxxx.SystemRootToken: secret token is not set (use 32+ random characters from a-z, A-Z, 0-9) 
ESC[33mWARNESC[0m[2021-02-09T11:02:21.924616505Z] Clusters.xxxxx.Collections.BlobSigningKey: secret token is not set (use 32+ random characters from a-z, A-Z, 0-9)

My cluster config has 64 chars alphanumeric entries for those tokens & keys in the cluster I'm deploying, but I guess those are pre-flight checks from arvados/lib/config/config.default.yml?


Subtasks 1 (0 open1 closed)

Task #17484: Review 17353-install-warningsResolvedLucas Di Pentima03/22/2021Actions
Actions #1

Updated by Peter Amstutz about 3 years ago

Do you have a /etc/arvados/config.yml already set up when you install the api server package? That's what it is checking. Those checks happen automatically on loading the config file. Some of the post-install steps of the api server automatically load the config file (possibly not strictly necessary but it is part of the initialization).

Actions #2

Updated by Peter Amstutz about 3 years ago

  • Target version changed from To Be Groomed to 2021-03-31 sprint
Actions #3

Updated by Ward Vandewege about 3 years ago

config-check's fault? It shouldn't apply warnings when loading the default config.

Actions #4

Updated by Ward Vandewege about 3 years ago

  • Release set to 39
Actions #5

Updated by Peter Amstutz about 3 years ago

  • Assigned To set to Tom Clegg
Actions #6

Updated by Tom Clegg about 3 years ago

  • Status changed from New to In Progress
Actions #7

Updated by Lucas Di Pentima about 3 years ago

This LGTM, thanks!

Actions #8

Updated by Tom Clegg about 3 years ago

  • Status changed from In Progress to Resolved
Actions #9

Updated by Ward Vandewege almost 3 years ago

  • Release changed from 39 to 38
Actions

Also available in: Atom PDF