Bug 1158656

Summary: your machine is running kernel 3.8.13-44.1.3 but a newer version (2.6.32-504) is installed
Product: [Fedora] Fedora EPEL Reporter: Thomas Schweikle <tschweikle>
Component: nagios-plugins-check-updatesAssignee: Jose Pedro Oliveira <jose.p.oliveira.oss>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: el6CC: jose.p.oliveira.oss, tschweikle
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-30 15:55:24 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:
Attachments:
Description Flags
Patched check_updates none

Description Thomas Schweikle 2014-10-29 19:55:42 UTC
Description of problem:
Install nagios-plugins-check-updates, then install some 3.x-Kernel in parallel to 2.x-Kernel. The Plugin will report:

CRIT - CHECK_UPDATES CRITICAL - your machine is running kernel 3.8.13-44.1.3 but a newer version (2.6.32-504) is installed: you should reboot, no updates available

Version-Release number of selected component (if applicable):
nagios-plugins-check-updates-1.6.3-1.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install nagios-plugins-check-updates; Install 3.x-Kernel along 2.x-Kernel
2. call /usr/lib64/nagios/plugins/check_updates
3. 

Actual results:
CRIT - CHECK_UPDATES CRITICAL - your machine is running kernel 3.8.13-44.1.3 but a newer version (2.6.32-504) is installed: you should reboot, no updates available

Expected results:
If 3.x-Kernel running: OK; if 2.x-Kernel running: OK too, if it is the last kernel in this line. If there is a kernel with a version number greater than the running one installed and it is within the same line report for reboot.

Additional info:

Comment 1 Thomas Schweikle 2014-10-29 19:56:05 UTC
Same with el5 and epel7

Comment 2 Thomas Schweikle 2014-10-29 19:57:02 UTC
Seems PackageKit has the same problem, reporting an out of date 3.x-Kernel is an 2.x-Kernel is installed too.

Comment 3 Thomas Schweikle 2014-10-29 23:36:09 UTC
Created attachment 951918 [details]
Patched check_updates

I've patched check_updates to work with Oracle uek-Kernels.

Comment 4 Jose Pedro Oliveira 2015-02-17 21:42:08 UTC
Hi,

Could you try to duplicate the problem with version 1.6.9 ? It's currently available in the testing repositories.  To upgrade just execute the following command:

 * yum update --enablerepo=epel-testing nagios-plugins-check-updates

or just download the rpm

 * https://dl.fedoraproject.org/pub/epel/testing/6/x86_64/nagios-plugins-check-updates-1.6.9-1.el6.x86_64.rpm

and manually install it (rpm -Fvh ...)

Could you also list the kernel rpms that you have installed on your system (rpm -q kernel) ?

Regards,
jpo

Comment 5 Ben Cotton 2020-11-05 16:49:57 UTC
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged  change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.

Comment 6 Ben Cotton 2020-11-30 15:55:24 UTC
EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
EPEL please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.