[LU-345] kernel and lustre version miss match for RHEL6 Created: 19/May/11  Updated: 28/May/17  Resolved: 28/May/17

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.1.0
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Sarah Liu Assignee: WC Triage
Resolution: Cannot Reproduce Votes: 0
Labels: None

Severity: 3
Rank (Obsolete): 10140

 Description   

Install lustre-master/RHEL6-x86_64 build with loadjenkinsbuild, kernel and lustre version miss match. Have to do insmod manually to install lustre modules.

For example, installing build #125 on fat-intel-1, lustre modules are under /lib/modules/2.6.32-71.18.2.el6_lustre.gce09fce.x86_64

[root@fat-intel-1 ~]# uname -a
Linux fat-intel-1.lab.whamcloud.com 2.6.32-71.29.1.el6.x86_64 #1 SMP Thu Apr 21 16:08:55 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux
[root@fat-intel-1 ~]# ls /lib/modules/
2.6.32-71.18.2.el6_lustre.gce09fce.x86_64 2.6.32-71.29.1.el6.x86_64



 Comments   
Comment by Peter Jones [ 19/May/11 ]

Brian

Can you please look at this one?

Thanks

Peter

Comment by Michael MacDonald (Inactive) [ 20/May/11 ]

This appears to be a problem with the EL6 installer. In short, even though the kickstart is specifying the correct kernel, EL6 is choosing the newest kernel it sees. This wasn't a problem until I added the latest errata kernel to the local yum mirror for EL6 (for LU-343).

As a short-term kludge, I can remove the 2.6.32-71.29.1.el6 kernel. Longer-term, this is a bug in EL6 (or a change in behavior that I consider a bug). I'll poke around in RH's bugzilla to see if this is a known issue which may have been addressed in EL6.1.

Comment by Michael MacDonald (Inactive) [ 20/May/11 ]

I've taken the kludgy approach for now and removed the 2.6.32-71.29.1.el6 kernel RPMs from the local mirror. I'll try to find a better solution soon, as this problem hinders our ability to test multiple kernel versions.

Comment by Michael MacDonald (Inactive) [ 14/Jun/11 ]

This ticket and TT-136 are basically for the same issue. As that ticket has been resolved, this one should be as well.

Comment by Sarah Liu [ 01/Aug/11 ]

got this issue again on the latest tag 2.0.66 build #228

[root@client-15 tests]# uname -a
Linux client-15.lab.whamcloud.com 2.6.32-131.6.1.el6.x86_64 #1 SMP Mon Jun 20 14:15:38 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux
[root@client-15 tests]# rpm -qa|grep lustre
lustre-client-tests-2.0.66-2.6.32_131.2.1.el6.x86_64.x86_64
lustre-client-modules-2.0.66-2.6.32_131.2.1.el6.x86_64.x86_64
lustre-client-2.0.66-2.6.32_131.2.1.el6.x86_64.x86_64

Comment by Michael MacDonald (Inactive) [ 01/Aug/11 ]

This is due to the requested EL6 kernel update. Due to the way EL6's anaconda works now, it is not possible to specify that an older kernel should be installed when a newer one is available in the repos.

Comment by Andreas Dilger [ 28/May/17 ]

This is no longer an issue.

Generated at Sat Feb 10 01:06:06 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.