domino_admin_toolkit.checks.test_central_config module
- domino_admin_toolkit.checks.test_central_config.central_config_data(k8s_client)
Collect central config data from the cluster.
- domino_admin_toolkit.checks.test_central_config.test_central_config(central_config_data)
- Description:
Displays the full Central Config table and runs analyzers to detect stale workarounds or misconfigured settings.
Central Config is where all global settings for a Domino installation are stored in MongoDB. This check makes the full table available for engineers to search, and flags known problematic values.
- Failure Conditions:
The domino.config collection is empty
useWorkloadService is set to false (stale workaround)
- Troubleshooting Steps:
If the collection is empty: confirm MongoDB is reachable (see test_mongodb) — a Mongo connection failure surfaces here too
If Mongo is healthy: check whether this cluster was recently restored via domino-data-importer’s restore –into-cluster new mode, which deliberately excludes domino.config so it can be repopulated on the destination cluster
For the stale-workaround case, review the CC table output for the flagged key, check Domino Admin UI or MongoDB directly for the current value, and cross-reference with recent support cases
- Resolution Steps:
If domino.config is empty from a migration/DR restore: repopulate central config on this cluster before proceeding — an empty central config leaves isRunningInKubernetes defaulted false, so Mongo resolves to 127.0.0.1 and nucleus hangs at boot
For stale workarounds: remove the CC override or set it back to the expected value via Domino Admin UI or MongoDB
Restart affected services after changing CC values
- Required Permissions:
Platform admin access
MongoDB read access (via toolkit service account)
- Public Facing KB:
https://docs.dominodatalab.com/en/latest/admin_guide/71d6ad/central-configuration/
- See also:
test_mongodb.py — disambiguates an empty result caused by an unreachable Mongo from a genuinely empty domino.config collection