ltsp-cluster SERVER variable is overwritten by ltsp_config file.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
LTSP5 |
Fix Released
|
Undecided
|
Marc Gariépy | ||
ltsp (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
Medium
|
Stéphane Graber | ||
Quantal |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
when booting a ltsp-cluster thin client I am unable to get my configuration because the variable SERVER is overwritten by the file /var/cache/
So we need to rename SERVER to CC_SERVER in getltscfg-cluster for it to work properly.
[test case]
configure your chroot to use ltsp-cluster.
run getltscfg-cluster -a
the server that it tryed to contact is the nbd-server
When the script is broken, getltscfg-cluster try to do a wget on the nbd-server instead if the control center.
With the patch, i changed the variable name to CC_SERVER to prevent the sourcing of /var/cache/
[regression potential]
None : The variable for the ltsp-cluster is changed to CC_SERVER in the script and configuration for ltps-cluster.
[development fix]
I know this section is deprecated but it's actually relevant in this case ;)
The fix hasn't hit quantal yet because of some massive packaging rework going on with LTSP to try and bring us in sync with Debian. I can guarantee that we will have a new upstream release in quantal that will include this fix. ETA is of a couple of weeks.
the patch can be found here:
http://
thanks
Changed in ltsp (Ubuntu Precise): | |
importance: | Undecided → Low |
assignee: | nobody → Stéphane Graber (stgraber) |
status: | New → Triaged |
Changed in ltsp (Ubuntu Quantal): | |
status: | New → Triaged |
Changed in ltsp: | |
status: | New → Fix Committed |
assignee: | nobody → Marc Gariépy (mgariepy) |
description: | updated |
Changed in ltsp (Ubuntu Precise): | |
status: | Triaged → In Progress |
importance: | Low → Medium |
description: | updated |
description: | updated |
Changed in ltsp (Ubuntu Quantal): | |
status: | Triaged → Fix Released |
Hi Marc.
Can you clarify the test case a bit? Its really hard to follow.. I'm not sure what to expect in the case where it is broken, or when it is fixed.
Thanks!