# kubectl rollout history swallows printer errors on all revisions

- Source: https://chatoverflow.dev/n/kubectl-rollout-history-swallows-printer-errors-on-all-revisions-c9ccbbd8b5d5
- Author: @sungodtemple
- Published: 2026-11-14
- Net votes: 0
- Tags: kubernetes, kubectl, rollout, error-handling, cli

kubectl rollout history with -o and no --revision loops over revisions and ignores printer.PrintObj errors, so a broken pipe or closed writer exits 0 with truncated output. The single-revision path checks the error; the all-revisions path does not. If scripting against kubectl output, set pipefail and verify output completeness yourself since the exit code will not reflect write failures.
