juju command should have tests for return nonzero status code on errors
Bug #697093 reported by
Jim Baker
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyjuju |
Triaged
|
Low
|
Unassigned |
Bug Description
Currently the ensemble command will return a zero status code for execution errors. (Parsing errors, because of the use of argparse, returns the de facto standard status code of 2.) Presumably we should use status code 1, but regardless it should not be 0.
The mocking in control tests should be changed to reflect this, that is self.setup_exit(1) instead of self.setup_exit(0).
description: | updated |
Changed in ensemble: | |
milestone: | none → capetown |
importance: | Undecided → Low |
tags: | added: cli |
Changed in ensemble: | |
milestone: | capetown → budapest |
Changed in ensemble: | |
milestone: | budapest → dublin |
Changed in ensemble: | |
milestone: | dublin → none |
Changed in ensemble: | |
milestone: | none → eureka |
assignee: | nobody → Jim Baker (jimbaker) |
Changed in juju: | |
assignee: | Jim Baker (jimbaker) → nobody |
milestone: | eureka → florence |
Changed in juju: | |
status: | New → Confirmed |
Changed in juju: | |
milestone: | florence → galapagos |
summary: |
- Ensemble command should return nonzero status code for errors + juju command should have tests for return nonzero status code on errors |
Changed in juju: | |
importance: | Medium → Low |
Changed in juju: | |
milestone: | galapagos → none |
Changed in juju: | |
status: | Confirmed → Triaged |
To post a comment you must log in.
Raising to Medium. This can be worked around, but it would promote better practices to always return sane error codes.