Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Don't consider stderr CLI output to be an error
Between RabbitMQ v3.8.14 and v3.8.15, the command `rabbitmq-queues rebalance quorum` outputs warn messages like `10:59:50.674 [warn] Node :"[email protected]" only contains 1 queues, do nothing` to stderr. Although this CLI command exits with 0, the operator considers this as a failure, retrying to execute that command. The operator logs the following: `2021-03-19T08:39:56.305Z ERROR controller-runtime.manager.controller.rabbitmqcluster Reconciler error {"reconciler group": "rabbitmq.com", "reconciler kind": "RabbitmqCluster", "name": "r1", "namespace": "default", "error": "failed to run queue rebalance on pod r1-server-0:` In general when CLI commands output to stderr, it doesn't mean that there was an error. So, in this commit we only consider non-zero exit codes as error.
- Loading branch information