Bug #17353

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

Added by Javier BĂ©rtoli 8 months ago. Updated 5 months ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
Deployment
Target version:
Start date:
03/22/2021
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
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

Task #17484: Review 17353-install-warningsResolvedLucas Di Pentima

Associated revisions

Revision 9e806b0c
Added by Tom Clegg 7 months ago

Merge branch '17353-install-warnings'

fixes #17353

Arvados-DCO-1.1-Signed-off-by: Tom Clegg <>

History

#1 Updated by Peter Amstutz 8 months 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).

#2 Updated by Peter Amstutz 7 months ago

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

#3 Updated by Ward Vandewege 7 months ago

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

#4 Updated by Ward Vandewege 7 months ago

  • Release set to 39

#5 Updated by Peter Amstutz 7 months ago

  • Assigned To set to Tom Clegg

#6 Updated by Tom Clegg 7 months ago

  • Status changed from New to In Progress

#7 Updated by Lucas Di Pentima 7 months ago

This LGTM, thanks!

#8 Updated by Tom Clegg 7 months ago

  • Status changed from In Progress to Resolved

#9 Updated by Ward Vandewege 5 months ago

  • Release changed from 39 to 38

Also available in: Atom PDF