landscape-config should exit gracefully in the event of client startup or DBUS connection failures
Bug #274819 reported by
Christopher Armstrong
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Landscape Client |
Fix Released
|
Undecided
|
Christopher Armstrong | ||
Landscape Server |
Fix Released
|
Undecided
|
Christopher Armstrong |
Bug Description
Right now ugly unknown error messages or tracebacks are printed when either
1. the client fails to be restarted (landscape-config calls /etc/init.
2. DBus isn't running
They should be suppressed with nicer error messages and followed by an exit with code 2.
An --ok-no-register option should exist to allow the exit code 2 to be replaced with exit code 0 in the event of a failed registration.
Related branches
Changed in landscape: | |
assignee: | nobody → radix |
status: | New → In Progress |
milestone: | none → thames-pre-9 |
Changed in landscape-client: | |
assignee: | nobody → radix |
status: | New → In Progress |
Changed in landscape-client: | |
status: | Fix Committed → Fix Released |
Changed in landscape: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The attached branch is based on trunk. Ready for review.