no service recovery notifications after host-check was just in soft-state

Bug #704505 reported by Thomas Kallenbach on 2011-01-18
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Nagios
Fix Released
Unknown
nagios3 (Debian)
Fix Released
Unknown
nagios3 (Ubuntu)
Medium
Unassigned
Lucid
Medium
Unassigned

Bug Description

Binary package hint: nagios3

Hello,

I've detected, that an old bug in nagios 3.2.0 is not fixed in nagios 3.2.0-4ubuntu2.

Bug in NagiosTracker: http://tracker.nagios.org/view.php?id=128

It was fixed in nagios-core 3.2.2

Would be nice if you could fix it for Ubuntu 10.04 LTS

Thank you very much.

My System:
---------------------------------------------
Description: Ubuntu 10.04.1 LTS
Release: 10.04

nagios3:
  Installed: 3.2.0-4ubuntu2
  Candidate: 3.2.0-4ubuntu2
  Version table:
 *** 3.2.0-4ubuntu2 0
        500 http://de.archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

Clint Byrum (clint-fewbar) wrote :

Ok, I added the link to the nagios bug report. I was going to nominate for Lucid and Maverick, which both carry versions of Nagios3 that have the bug, but I don't see the link on Launchpad to do that anymore.

Marking as Triaged, and adding link to forwarded Debian bug report. Hopefully package maintainers can nominate this bug for Lucid/Maverick somehow.

Changed in nagios3 (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Changed in nagios:
status: Unknown → Fix Released
Changed in nagios3 (Debian):
status: Unknown → Confirmed
Changed in nagios3 (Ubuntu Lucid):
importance: Undecided → Medium
status: New → Triaged
Rolf Leggewie (r0lf) wrote :

lucid has seen the end of its life and is no longer receiving any updates. Marking the lucid task for this ticket as "Won't Fix".

Changed in nagios3 (Ubuntu Lucid):
status: Triaged → Won't Fix
Changed in nagios3 (Debian):
status: Confirmed → Fix Released
Nish Aravamudan (nacc) wrote :

Note that the Debian bug was closed with +rm, meaning the package has now been deleted from Debian. This may end up happening in Ubuntu too, but means that the only choice would be to SRU the upstream fix back to the appropriate distributions. However, upstream is also focusing on nagios4, so perhaps another choice should be made.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.