Bug 47223 – No nrpe after failed update

Bug 47223 - No nrpe after failed update


Summary:	No nrpe after failed update

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Monitoring (Prometheus or Nagios)
Version:	UCS 4.3
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:	46559
Blocks:
	Show dependency tree / graph

Reported:	2018-06-21 08:34 CEST by Philipp Hahn
Modified:	2021-05-14 16:34 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?:	3: Will affect average number of installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.171
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Philipp Hahn

2018-06-21 08:34:28 CEST

The nrpe daemon is stopped in preup to prevent Bug #46559.
If the update fails, it is not restarted.
This currently breaks Nagios on all our KVM servers every night (as there unsigned repository are included and the `apt-get dist-upgrade` aborts with exit code 100).

+++ This bug was initially created as a clone of Bug #46559 +++

Comment 1 Ingo Steuwer

2021-05-14 13:56:15 CEST

This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.