GB-194: the edge cannot be admitted on our core¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-194 is printed by goatbuilder. The same text offline: goat explain GB-194 or goatbuilder explain GB-194.
What it means¶
Phase 10 by the command (confirmation 2) did not change our core: the agreement digest has not been confirmed with the partner for the agreement in place, --approve-admission names another digest (something changed since it was read), the deployment does not say where our core's access control lives or how it restarts, their CA does not match the agreement, or the fragment could not be merged, assembled or placed (what was placed is put back).
Why it happens¶
- phase 6 ran without --agreement-digest (or --confirm), so the digest was never compared
- the files were rendered again after the summary was read
- FED_CORE_ACL_ORG, FED_CORE_PLAY or FED_CORE_RESTART, or FED_SLOT_* is not set
- their CA file holds more than the one certificate the agreement names
What to do¶
One line per step or alternative:
compare the digest with the partner: goatbuilder federate <partner> --from 6 --to 6 --agreement-digest <digest>
read the summary again and approve the digest it shows now
set the FED_CORE_* settings in the deployment's environment, or run without the admission flags so phase 10 stops, admit by hand, and run --from 11
Read more¶
Exit code¶
goatbuilder exits with 1.