Client does not return the correct exit code when failing to communicate with server.
Bug #1434546 reported by
Chris Glass
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Landscape Client |
Fix Released
|
Medium
|
Chris Glass | ||
landscape-client (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Trusty |
New
|
Undecided
|
Unassigned |
Bug Description
As part of the fallout from recent changes in the client configuration, the trunk client does not exit the same way as before.
One error, the previous client did and "exit(2)" (and exit(1) should the configuration file be unreadable)
We should at least reinstate the exit(2) behavior since robot tests rely on it and it is a reasonable assumption that a program returns a non-zero exit code on failure.
Related branches
lp://staging/~tribaal/landscape-client/1434546-wrong-exit-code-on-error
- Benji York (community): Approve
- Free Ekanayaka (community): Approve
-
Diff: 118 lines (+33/-8)2 files modifiedlandscape/configuration.py (+10/-2)
landscape/tests/test_configuration.py (+23/-6)
lp://staging/~tribaal/landscape-client/take-two-1434546-exit-code-2-on-error
- Alberto Donato: Approve
- Benji York (community): Approve
-
Diff: 183 lines (+67/-11)2 files modifiedlandscape/configuration.py (+13/-2)
landscape/tests/test_configuration.py (+54/-9)
description: | updated |
tags: | removed: kanban |
Changed in landscape-client: | |
status: | New → Fix Committed |
Changed in landscape-client: | |
milestone: | none → 15.04 |
Changed in landscape-client: | |
status: | Fix Committed → Fix Released |
Changed in landscape-client: | |
status: | Fix Released → Fix Committed |
Changed in landscape-client: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.