GB-048: the goatnet is not proven built¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-048 is printed by goatbuilder. The same text offline: goat explain GB-048 or goatbuilder explain GB-048.
What it means¶
the acceptance assay ran and at least one applicable row failed, or could not answer, or no row passed. Only PASS counts toward done; an UNKNOWN row is a row nobody proved (ADR 1115).
Why it happens¶
- a FAIL row is the goatnet failing that check; its caught_would_have text says what it means
- an UNKNOWN row could not be probed from here, most often a goat CLI row run where no goat context with a fabric identity exists (E_PROFILE_MISSING)
- a SKIPPED negative row whose paired positive did not pass
What to do¶
One line per step or alternative:
goatbuilder assay <site> --only <row-id> (re-run one row after a fix)
goatbuilder assay <site> --var goat_via=<user@host> (run the goat CLI rows where a goat context is)
goatbuilder assay <site> --plan (which rows apply to this site)
Read more¶
Exit code¶
goatbuilder exits with 3.