ui-settings: notification says "failed to connect" when the error reported by landscape-config was "wrong account name or password"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Landscape Client |
Fix Released
|
Low
|
Free Ekanayaka |
Bug Description
root@nsn7:~# landscape-config --silent
* Stopping landscape-client daemon [ OK ]
* Starting the landscape-client daemon [ OK ]
Please wait... Invalid account name or registration password.
root@nsn7:~# echo $?
2
But the notification bubble says:
"""Failed to connect to Landscape server"""
This was selecting LDS and pointing it at staging.
Unfortunately if the user is only using the UI, there is no way to discover the real error other than running landscape-config --silent at the console. The broker logs don't have the error either:
"""
2012-03-15 10:57:08,848 INFO [MainThread] Queueing message to register with account 'standalone' with a password.
2012-03-15 10:57:08,852 INFO [MainThread] Starting urgent message exchange with https:/
2012-03-15 10:57:10,643 INFO [PoolThread-
2012-03-15 10:57:10,649 INFO [MainThread] Switching to normal exchange mode.
2012-03-15 10:57:10,654 INFO [MainThread] Message exchange completed in 1.80s.
"""
Related branches
- Mike Milner (community): Approve
- Fernando Correa Neto (community): Abstain
- Chad Smith: Approve
-
Diff: 84 lines (+16/-10)3 files modifiedlandscape/ui/model/registration/mechanism.py (+11/-5)
landscape/ui/model/registration/tests/test_mechanism.py (+4/-4)
landscape/ui/model/registration/tests/test_proxy.py (+1/-1)
Changed in landscape-client: | |
assignee: | nobody → Free Ekanayaka (free.ekanayaka) |
status: | New → In Progress |
Changed in landscape-client: | |
status: | In Progress → Fix Committed |
Changed in landscape-client: | |
status: | Fix Committed → Fix Released |