GB-195: the core's dry run or the slot check refused the admission¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-195 is printed by goatbuilder. The same text offline: goat explain GB-195 or goatbuilder explain GB-195.
What it means¶
After placing the new access control (nothing loads it before a restart), the core router's dry run failed, or the committed slot list differs from the registry or the registry could not be read. Restarting now could drop or add stores, so the files placed were put back and the core was not restarted.
Why it happens¶
- the assembled configuration does not pass the core's play in check mode
- the slot list in the repository is behind the registry
What to do¶
One line per step or alternative:
run the dry run by hand to read why (the message prints it)
regenerate the slot list with ops/scripts/sync-slot-anchors.py, commit it, deploy the core, then run phase 10 again
Read more¶
Exit code¶
goatbuilder exits with 1.