Skip to content

GB-190: the admission on our core is not recorded as done for what is rendered now

Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-190 is printed by goatbuilder. The same text offline: goat explain GB-190 or goatbuilder explain GB-190.

What it means

deploy --from 11 skips phase 10, the by-hand admission of the partner's edge on our core, so it runs only when the journal records phase 10 as done for exactly the files rendered now. It does not, so nothing changed: either the admission was never declared, or the rendered files changed after it.

Why it happens

  • deploy has not stopped at phase 10 yet, so the admission was never done for these files
  • the files were rendered again after the admission was declared

What to do

One line per step or alternative:

goatbuilder federate deploy <partner> --approve-plan <hash> (it stops at phase 10; do the admission, then run it again with --from 11)

Read more

Exit code

goatbuilder exits with 1.