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-4951 Lustre <p>As part of TEI-1359 work to integrate DKMS RPM build+test in our tools chain, it hs been found that DKMS RPM fails during its post-installation when it tries to rebuild Lustre modules for the current/installed Kernel.<br/> It fails complaining about the fact lvfs.ko module has not been built, but this because actual dkms.conf still references lvfs module when it has been removed as part of <a href="https://jira.whamcloud.com/browse/LU-2158" title="remove lvfs and fsfilt code" class="issue-link" data-issue-key="LU-2158"><del>LU-2158</del></a>.</p> <p>First+quick patch will be to change/refresh dkms.conf with only currently generated modules. Next work will be to find a way to dynamically populate dkms.conf with the accurate modules.</p> LU-4951

DKMS RPM no longer works due to referencing removed modules in its current configuration

Bug Critical Resolved Fixed Bruno Faccini Bruno Faccini prz Thu, 24 Apr 2014 10:44:18 +0000 Thu, 4 Jun 2015 14:30:09 +0000 Fri, 23 Jan 2015 05:20:55 +0000 Lustre 2.6.0 Lustre 2.7.0 0 6 <p>This kind of drift between expected and actual modules was one of my original concerns with the static module list used for DKMS. Since the list does not change frequently, and we do not build DKMS packages as part of our build process, it is easy to forget changing the spec file. We definitely need the module list to be dynamically generated. </p> <p>PS: I'm not against making the quick fix first. </p> <p>Sure Andreas! Here it is, <a href="http://review.whamcloud.com/10090" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/10090</a>.</p> <p>Patch has landed.</p> <p>Faccini Bruno (bruno.faccini@intel.com) uploaded a new patch: <a href="http://review.whamcloud.com/12784" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/12784</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-4951" title="DKMS RPM no longer works due to referencing removed modules in its current configuration" class="issue-link" data-issue-key="LU-4951"><del>LU-4951</del></a> scripts: remove nodemap.ko in dkms.conf<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: ac5e95a4049b68af8ad0b20485c6200cf561c629</p> <p>A new+similar problem has appeared since <a href="https://jira.whamcloud.com/browse/LU-4647" title="Add idmapping functions for nodemap" class="issue-link" data-issue-key="LU-4647"><del>LU-4647</del></a> patch (Gerrit change #9299, at <a href="http://review.whamcloud.com/9299" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/9299</a>, Commit 83f04354ff68a14d7492e35a9576c91492a1206c) has landed in master (between tags 2.6.54 and 2.6.90) and has removed nodemap.ko module.</p> <p>I have just pushed a new/2nd quick fix/patch to master for this at <a href="http://review.whamcloud.com/12784" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/12784</a>.</p> <p>Doing so, I was trying to figure out how I can reliably modify the current creation process for dkms.conf file in order to dynamically detect from a particular Lustre version/source-tree:<br/> 1) modules that must always be built, with Client/Server distinction. <br/> 2) but may be also modules that will only build depending on configure-time discovery, like for ptlrpc_gss.ko ?<br/> 3) any other cause with impact on module creation?</p> <p>I imagine by setting dependencies right we can avoid configure since we know we always have everything we need.</p> <p>Oleg Drokin (oleg.drokin@intel.com) merged in patch <a href="http://review.whamcloud.com/12784/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/12784/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-4951" title="DKMS RPM no longer works due to referencing removed modules in its current configuration" class="issue-link" data-issue-key="LU-4951"><del>LU-4951</del></a> scripts: remove nodemap.ko in dkms.conf<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: 78afe76bd723df1736e4323ae3ccb42fd961c218</p> <p>It looks like the latest fix has landed to 2.7</p> Related LU-2158 Development Rank 1|hzwkwv: Rank (Obsolete) 13699 Severity