Bug 694421

Summary:	iotop requires kernel-2.6.18-199.el5 or later, but kernel-2.6.18-194.32.1.el5 is running
Product:	[Fedora] Fedora EPEL	Reporter:	David Busby <d.busby>
Component:	iotop	Assignee:	Michal Hlavinka <mhlavink>
Status:	CLOSED CANTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	el5	CC:	mhlavink
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-04-11 09:03:25 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description David Busby 2011-04-07 10:26:26 UTC

Description of problem:

iotop installs from EPEL, onto kernel  kernel-2.6.18-194.32.1.el5, 
however it requires kernel-2.6.18-199.el5

I have verified the iotop.spec file also contains this requirement

"""
Requires: python python-ctypes
Requires: kernel >= 2.6.18-199
"""

rpm -qR iotop
/usr/bin/python  
kernel >= 2.6.18-199
python  
python(abi) = 2.4
python-ctypes  


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

0.4.1-2.el5


How reproducible:

Install from epel and attempt to run.

Steps to Reproduce:

As above
  
Actual results:

iotop requires kernel-2.6.18-199.el5 or later, but kernel-2.6.18-194.32.1.el5 is running

Expected results:

iotop running, or failure to install due to missing dependency.

Additional info:

Comment 1 Michal Hlavinka 2011-04-11 09:03:25 UTC

This can't be fixed. Kernel packages provides virtual 'kernel' and 'kernel-version' (and few others) but the first one means 'all versions', so iotop can't require specific version. This can be workarounded by requiring kernel-arch-version, but iotop is noarch package, so we can't use this here. Anyway, even when correct kernel is installed it does not mean that required kernel is also running. Closing as cantfix. Also correct kernel was released in rhel 5.6, so once you update your kernel (and boot it), it should be working fine.

Comment 2 David Busby 2011-04-11 09:58:49 UTC

Thanks for the feedback, I have this running fine on some of our EL6 deploys, this just struck me as odd when I was deploying to some of our older machines, one more reason to add to the "justifications for upgrade".