Skip to content

GB-260: a rollback has no history to go back to, or its target is refused

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

What it means

rollback goes back through the host's deploy ledger and the in-repo history (deploy-history.yml). There is no history for the component, not enough of it, or the ref it would roll to is flagged do_not_roll_to, or a host runs a ref neither history knows.

Why it happens

  • the component has not been adopted into deploy-history.yml
  • the history holds fewer entries than the rollback asks for
  • the target ref is flagged do_not_roll_to in the in-repo ledger
  • a host runs a ref no history records (deployed by hand?)

What to do

One line per step or alternative:

goatbuilder rollback <component> --status
investigate the host the message names before rolling back

Read more

Exit code

goatbuilder exits with 2.