Bug #17353
closed
[deployment] Misleading WARNING messages on arvados-api-server install?
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?
Updated by Peter Amstutz almost 4 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).
Updated by Peter Amstutz over 3 years ago
- Target version changed from To Be Groomed to 2021-03-31 sprint
Updated by Ward Vandewege over 3 years ago
config-check's fault? It shouldn't apply warnings when loading the default config.
Updated by Tom Clegg over 3 years ago
- Status changed from New to In Progress
17353-install-warnings @ 767b749993089167120a533e43dc4b4e318bccde -- developer-run-tests: #2384
Updated by
Updated by Tom Clegg over 3 years ago
- Status changed from In Progress to Resolved
Applied in changeset arvados|9e806b0c387cf7146e0d0cf3169fd227963c19b9.