Bug 1273148

Summary:	[RFE] Provide a yum health check plugin that provides compatibility check and reboot requirement advice
Product:	Red Hat Enterprise Linux 7	Reporter:	Dave Sullivan <dsulliva>
Component:	yum	Assignee:	Valentina Mukhamedzhanova <vmukhame>
Status:	CLOSED NOTABUG	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3	CC:	james.antill, rsawhill
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-06-02 17:23:01 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dave Sullivan 2015-10-19 18:34:35 UTC

Description of problem:

Updates can be done on a system within a RHEL major release that causes soname changes or even ABI differences.

e.g.

https://bugzilla.redhat.com/show_bug.cgi?id=1183760#c17

So the request here is to provide a yum plugin that serves a system/health check.

In addition to notifying the user of potential soname/abi issues it can also advise on when certain services need to be reviewed and restarted

e.g. I've seen http updates they drop a httpd.conf.new file in and I've the old httpd.conf file references modules that have been removed

here we should be able to advise that http will have problems on restart

Also when glibc and/or kernel and maybe some other files are updated we probably should advise that restart of the systems is in order.


Version-Release number of selected component (if applicable):

Current 7.2 Beta

Expected results:

See above

Additional info:

Comment 2 Dave Sullivan 2015-10-19 20:08:14 UTC

A couple references

https://www.redhat.com/archives/rhl-list/2009-July/msg00191.html

Which packages require a system reboot after update?
https://access.redhat.com/solutions/27943

Comment 3 Valentina Mukhamedzhanova 2016-06-02 17:23:01 UTC

Hello Dave,

As I can see, this RFE suggests several separate enhancements. We have a couple of RFEs which we will include in the 7.3 yum-utils erratum:

Bug 1192946 adds the --reboothint flag to the needs-restarting command. It addresses the situation when a customer wants to check if the system should be rebooted after the upgrade.

Bug 1335587 adds the --services flag to the needs-restarting command. This flag maps PIDs to systemd services and displays an informative table. This helps with figuring out which of the currently running services should be restarted.

And finally, yum has the 'updateinfo' command which allows reviewing the upgrade details before running 'yum upgrade'. Individual packages may provide warnings as part of the updateinfo metadata.

I've also read the attached customer case, but I don't quite see how it is related to this RFE.

As we have other BZs for tracking the functionality mentioned above, I'm closing this BZ.