Landscape client motd updater refers to wrong LS server when using LDS
Bug #1091531 reported by
Brad Marshall
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Landscape Client |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
The landscape client motd updater refers to the wrong Landscape server when the host is talking to an LDS instance.
From a host registered with an internal LDS system:
$ landscape-sysinfo | grep Graph
Graph this data and manage this system at https:/
I believe this should point to the correct URL instead of landscape.
This occurs on at least both precise and lucid, the example here is from a lucid host with the following version of landscape-client.
$ dpkg-query -W landscape-client
landscape-client 12.05-0ubuntu1.
Please let me know if you need any further information.
Revision history for this message
| Thomas Herve (therve) wrote | #1 |
| Changed in landscape-client: | |
| milestone: | none → backlog |
| importance: | Undecided → Low |
Revision history for this message
| Brad Marshall (brad-marshall) wrote | #2 |
| tags: | added: is |
Revision history for this message
| 🤖 Landscape Builder (landscape-builder) wrote | #3 |
| Changed in landscape-client: | |
| status: | New → Invalid |
| Changed in landscape-client: | |
| status: | Invalid → New |
| Changed in landscape-client: | |
| status: | New → Triaged |
| tags: | added: squad-bug |
| Changed in landscape-client: | |
| importance: | Low → Wishlist |
To post a comment you must log in.
This message is generally intended to machines which don't use landscape client just yet. So I'm wondering what the proper thing to do: should we just remove the message if the machine is registered is Landscape? Or do you see value in the message staying there, but pointing to the proper URL?