Skip to content

GB-039: a rollback on a fixture needs its environment

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

What it means

on a fixture (--mock) a rollback declares the earlier ref in one environment and converges it there, so it needs --env; --list and --status read host ledgers, which a fixture does not have.

Why it happens

  • --mock given without --env
  • --list or --status given with --mock

What to do

One line per step or alternative:

goatbuilder --mock <fixture> rollback <component> 1 --env <env> --ack "<your name>" --dry-run
goatbuilder --mock <fixture> status --env <env> (the state a fixture has)

Read more

Exit code

goatbuilder exits with 2.