Skip to content

GB-063: a standup step's host limit selects no host

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

What it means

The plan runs this play with --limit <pattern>, and the pattern matches no host of the target group in the inventory, so the play runs on nothing and reports success.

Why it happens

  • the limit assumes the mgmt-<site>-01 host naming and this site names its hosts differently
  • the step installs a service this joining site does not run yet, which its end state names as a gap with the gate row that closes it

What to do

One line per step or alternative:

goatbuilder endstate <site> names each gap with its gate row (I1, I4 for an admin surface); a gap is work still to build, not a reason to skip the step
if it should, fix the limit in goat-standup.sh and goatbuilder standup together

Read more

Exit code

goatbuilder exits with 0.