Skip to content

GB-070: survey could read no goatnet at all

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

What it means

survey reads every goatnet it was asked for in parallel and reports what it could not read as unknown. When not one goatnet answered, there is nothing to compare, and the run stops instead of printing an empty survey that would look consistent.

Why it happens

  • this laptop is on no goatnet's mesh profile and no door opened (no AWS credentials for the SSM door)
  • every goatnet named with --env is misspelled or not in ops/pins/fleet-pins.yaml
  • ansible is not installed, or ops/scripts/with-aws cannot run

What to do

One line per step or alternative:

goatbuilder doctor --env <goatnet> --all names the transport each goatnet would use and what is missing
name goatnets by their fleet-pins key: --env <goatnet> (repeatable)

Read more

Exit code

goatbuilder exits with 1.