UI settings: if server is unreachable, the error isn't caught
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Landscape Client |
Fix Released
|
High
|
Geoff Teale |
Bug Description
I used the UI to point my client to a local landscape deployment, on 10.0.1.11:8080. Turns out the UI tool defaults to https, which is fine, but which my server wasn't using, so it timed out eventually:
broker.log:
2012-03-07 14:33:22,291 ERROR [PoolThread-
Traceback (most recent call last):
File "/usr/lib/
curly, data = self._curl(
File "/usr/lib/
headers=
File "/usr/lib/
raise PyCurlError(
PyCurlError: Error 28: SSL connection timeout at 29938
2012-03-07 14:33:22,293 INFO [MainThread] Message exchange failed.
But another timeout is in play it seems, related to dbus. The ui settings app just crashed with this backtrace:
andreas@
Traceback (most recent call last):
File "/usr/lib/
self.on_fail)
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
error_
File "/usr/lib/
**keywords)
File "/usr/lib/
message, timeout)
dbus.exceptions
I just verified and the UI settings app crashed before the broker reported the error.
Related branches
- Thomas Herve (community): Approve
- Free Ekanayaka (community): Approve
-
Diff: 191 lines (+90/-16)5 files modifiedlandscape/ui/controller/app.py (+14/-11)
landscape/ui/controller/configuration.py (+3/-1)
landscape/ui/controller/tests/test_app.py (+2/-1)
landscape/ui/model/registration/proxy.py (+13/-3)
landscape/ui/model/registration/tests/test_proxy.py (+58/-0)
description: | updated |
Changed in landscape-client: | |
status: | New → In Progress |
assignee: | nobody → Geoff Teale (tealeg) |
Changed in landscape-client: | |
status: | In Progress → Fix Committed |
Changed in landscape-client: | |
status: | Fix Committed → Fix Released |