You are interested in having this bug fixed in a SRU (stable release update) for hardy. I am closing it as "Fix released" because the bug has been fixed in the latest development version of Ubuntu - the Intrepid Ibex.
If you need a fix for the bug in previous versions of Ubuntu, please follow the SRU Procedure [1] to bring the need to a developer's attention.
In particular you should use "Nominate for release" to target it for a hardy update.
I set it to "Low" because I couldn't think of something that would break due to that wrong return code. Could you please explain your heartbeat scenario so that the bug priority is set up properly ?
You are interested in having this bug fixed in a SRU (stable release update) for hardy. I am closing it as "Fix released" because the bug has been fixed in the latest development version of Ubuntu - the Intrepid Ibex.
If you need a fix for the bug in previous versions of Ubuntu, please follow the SRU Procedure [1] to bring the need to a developer's attention.
[1]: https:/ /wiki.ubuntu. com/StableRelea seUpdates
In particular you should use "Nominate for release" to target it for a hardy update.
I set it to "Low" because I couldn't think of something that would break due to that wrong return code. Could you please explain your heartbeat scenario so that the bug priority is set up properly ?