Client does not return the correct exit code when failing to communicate with server.

Bug #1434546 reported by Chris Glass on 2015-03-20
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Landscape Client
Medium
Chris Glass
landscape-client (Ubuntu)
Undecided
Unassigned
Trusty
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

Chris Glass (tribaal) on 2015-03-20
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.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers