** Description changed:
We got smart hanging on two machines (ls2 and ls5) with an open
connection (smart update run via cron). It is still being debugged, but
it looks like adding some sort of timeout for the connections would help
to avoid this situation.
+
+ The Landscape team has proposed an SRU to fix this bug in intrepid and
+ jaunty:
+
+ Statement explaining the impact
+ =====================
+
+ This fix is critical, as we had customer installations being bitten by
+ this bug before. Smart would just hang there, doing nothing but blocking
+ itself. As a result, landscape would not be able to manage the packages
+ of this machine.
+
+ How the bug has been addressed
+ ======================
+
+ Introducing a timeout for the libcurl call.
+
+ Detailed instructions how to reproduce the bug
+ ==============================
+
+ It can be reproduced artificially by inducing a timeout by means of
+ traffic shaping. It has been done by the Landscape QA engineer and the
+ fix is confirmed to work as expected.
** Project changed: landscape => landscape-client
** Changed in: landscape-client
Milestone: mountainview => None
** Changed in: landscape-client
Milestone: None => 1.3.2.1
** Also affects: smart (Ubuntu)
Importance: Undecided
Status: New
--
add timeout for smart connections
https://bugs.launchpad.net/bugs/268261
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
