https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-8519 Lustre <p>I don't know when it broke, but currently server builds on sles12 generate .rpm packages that can't install without --nodeps or --force. The problem appears to be with the Provides and Requires strings in the various <b>kmp</b> packages. They don't match.</p> <p>I'm guessing it's been broken for a while and just hasn't been noticed. Maybe not noticed because we seldom test with sles12 server builds or maybe our test framework installs with --force options or something.</p> <p>Here is what I see in packages from a recent sles12 server build in lustre-reviews:</p> <p>rpm -q --provides -p lustre-kmp-default-2.8.56_34_gf7472b3_k3.12.60_52.54-1.x86_64.rpm | grep lustre-kmp<br/> lustre-kmp = 2.8.56_34_gf7472b3<br/> lustre-kmp = 2.8.56_34_gf7472b3_k3.12.60_52.54</p> <p>rpm -q --requires -p lustre-osd-ldiskfs-kmp-default-2.8.56_34_gf7472b3_k3.12.60_52.54-1.x86_64.rpm | grep lustre-kmp<br/> lustre-kmp = 2.8.56_34_gf7472b3_k3.12.59_60.41_lustre</p> <p>Note the Requires string has '41_lustre' on the end and the Provides string has '_52.54'. They don't match at all.</p> <p>I'm guessing this has something to do with one of the many recent changes in the lustre.spec.in file.</p> LU-8519

build is broken on sles12

Bug Critical Resolved Fixed Minh Diep Bob Glossman Fri, 19 Aug 2016 19:48:05 +0000 Sat, 8 Oct 2016 19:08:13 +0000 Sat, 8 Oct 2016 19:08:13 +0000 Lustre 2.9.0 Lustre 2.9.0 0 8 <p>the current kernel version of sles12 is supposed to be 3.12.59-60.41</p> <p>looks like rpm names are kind of mashed up too.</p> <p>I'm guessing the 'k3.12.60_52.54' showing up in some strings and package names is coming from the kernel version of the kernel running on the sles builder, not the kernel version of the kernel in lustre's '--with-linux=' configure option.</p> <p>I note that I can see quite varying package names even in client builds. for example lustre-client-kmp-default-2.8.56_42_g7ac162e_k3.12.57_60.35-1.x86_64.rpm in <br/> <a href="https://build.hpdd.intel.com/job/lustre-reviews/41080/arch=x86_64,build_type=client,distro=sles12,ib_stack=inkernel" class="external-link" target="_blank" rel="nofollow noopener">https://build.hpdd.intel.com/job/lustre-reviews/41080/arch=x86_64,build_type=client,distro=sles12,ib_stack=inkernel</a></p> <p>That has '3.12.57' in the name, even farther from what I think should be there.</p> <p>The lustre source code and the %kernel_module_package macro used by the lustre.spec file determine which kernel to compile against using different methods. For RHEL-like systems we override a variable that used internally in RHEL's kernel_module_package macro:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre> 26 # We set this because kernel_module_package has its own method of identifying 27 # which kernel to build against, and it is unlikely that its decision will 28 # match with Lustre's method of selecting which kernel to build against. 29 # By setting this variable, we override kernel_module_package's kernel 30 # selection with our selection. 31 %{!?kernel_version: %global kernel_version %kversion} </pre> </div></div> <p>We get away with this kludge because the RHEL kernel_module_package does this:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>%{!?kernel_version:%{expand:%%global kernel_version %{latest_kernel}}} </pre> </div></div> <p>That allows kernel_version to be predefined elsewhere (by us in this case), overriding the function's own logic.</p> <p>This is also probably a problem largely created by lbuild. Because lbuild doesn't install Lustre prerequisites like the kernel packages in their proper location, none of the standard system rpm packaging tools will be able to find it.</p> <p>SLES's kernel_module_package does not seem to have the same easy kernel_version override like RHEL's kernel_module_package. It is probably going to be tricky to fix this in lbuild.</p> <p>Minh Diep (minh.diep@intel.com) uploaded a new patch: <a href="http://review.whamcloud.com/22484" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/22484</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-8519" title="build is broken on sles12" class="issue-link" data-issue-key="LU-8519"><del>LU-8519</del></a> build: debug sles build<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 21527295621e42dc61e95623976902cb337e4e4e</p> <p>Oleg Drokin (oleg.drokin@intel.com) merged in patch <a href="http://review.whamcloud.com/22484/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/22484/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-8519" title="build is broken on sles12" class="issue-link" data-issue-key="LU-8519"><del>LU-8519</del></a> build: make SLES use lbuild kernel-devel<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: 0f9c4747281679d90497d8128239379daa5a1bc8</p> <p>Landed for 2.9</p> Related LU-5614 Development Rank 1|hzylf3: Rank (Obsolete) 9223372036854775807 Severity