Client doesn't write ping interval back to file.
Bug #1039550 reported by
Geoff Teale
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Landscape Client |
Fix Released
|
Low
|
Geoff Teale | ||
Bug Description
Originally reported by Chad in the server side branch ( https:/
"landscape-client branch doesn't actually seem to write the ping-interval updated value to the client.conf file. If my /tmp/root-conf. The client config file does get written (and timestamp is updated), but it retains the original client setting for the ping-interval value. This will cause us a problem upon client restart, where the client falls back to the original settings."
Related branches
lp:~tealeg/landscape-client/write-ping-time-back-to-config
- Chris Glass (community): Approve
- Thomas Herve (community): Approve
-
Diff: 154 lines (+36/-21)5 files modifiedlandscape/broker/ping.py (+13/-9)
landscape/broker/service.py (+1/-2)
landscape/broker/tests/helpers.py (+2/-2)
landscape/broker/tests/test_exchange.py (+2/-2)
landscape/broker/tests/test_ping.py (+18/-6)
| Changed in landscape-client: | |
| assignee: | nobody → Geoff Teale (tealeg) |
| Changed in landscape-client: | |
| status: | New → In Progress |
| Changed in landscape-client: | |
| milestone: | none → 12.10 |
| importance: | Undecided → Low |
| Changed in landscape-client: | |
| status: | In Progress → Fix Committed |
| Changed in landscape-client: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
