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-3450 Lustre <p>To reproduce:</p> <ul> <li>Install Lustre 2.1.x on server A</li> <li>Create a yum repository serving Lustre 2.3.x packages on server B</li> <li>Edit yum configuration on server A to point to new repo on server B</li> <li>Run "yum update lustre" on server A</li> </ul> <p>Expected outcome:</p> <ul> <li>All the Lustre packages on Server A upgraded to the 2.3.x versions</li> </ul> <p>Actual outcome:</p> <ul> <li>All the Lustre packages except lustre-ldiskfs are upgraded &#8211; lustre-ldiskfs remains at the 2.1.x version, causing subsequent filesystem mounts to fail due to the old version of ldiskfs.</li> </ul> <p>Background:</p> <ul> <li>lustre-modules depends on lustre-backing-fs, which is provided by lustre-ldiskfs. However, there are no versions specified in this dependency chain, so when a 2.1.x lustre-ldiskfs is already installed, that satisfies the dependency of the lustre 2.3.x lustre-modules. As a result, yum sees no need to install the updated ldiskfs package.</li> </ul> <p>Suggested fix:</p> <ul> <li>Make lustre-modules depend on a specific version of lustre-backend-fs or lustre-ldiskfs</li> </ul> LU-3450

lustre-ldiskfs upgrades don't get installed when upgrading from yum

Story Major Open Unresolved Minh Diep John Spray mq213 Tue, 11 Jun 2013 10:43:10 +0000 Fri, 28 Jun 2013 21:41:33 +0000 Lustre 2.3.0 Lustre 2.1.6 0 5 <p>Just so that reproducing this doesn't get hung up in trying to create yum repos, etc. an equally valid reproducer is to simply upgrade a Lustre 2.1.x system to Lustre 2.3.0 but DO NOT include the lustre-ldiskfs RPM in your rpm upgrade operation. So, i.e.:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"># rpm -Uvh lustre-2.3.0-2.6.32_279.5.1.el6_lustre.gb16fe80.x86_64.x86_64.rpm lustre-modules-2.3.0-2.6.32_279.5.1.el6_lustre.gb16fe80.x86_64.x86_64.rpm </pre> </div></div> <p>That command should happily work without error. The problem is however, that as John says, the lustre-ldiskfs that got left back from the 2.1.5 installation simply doesn't work with Lustre 2.3.0 and so the packaging needs to ensure that a compatible ldiskfs is pulled in (i.e. required).</p> <p>This is probably as simple as adding versioning to the "Provides: lustre-backing-fs" in the ldiskfs specfile and a corresponding versioning to the "Requires: lustre-backing-fs" thats in the lustre specfile. If you want to maintain some amount of flexibility in matching ldiskfs to Lustre, you can use &gt;= operators in your Requires:.</p> <p>Minh</p> <p>Could you please help with this one?</p> <p>Thanks</p> <p>Peter</p> <p>This problem is unfortunately caused by the ldiskfs RPM not changing its version for some time, and also the Lustre code not depending on a particular ldiskfs RPM version (though increasing the version wouldn't have helped in itself).</p> <p>For IEEL and 2.1.6 the ldiskfs build version needs to be modified (to 3.3.6 for 2.1.6, and 3.4.1 for IEEL), and then add a <tt>Requires: lustre-ldiskfs =</tt> for those versions in the lustre.spec.in file. See <a href="http://review.whamcloud.com/5938" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/5938</a> for how this was done for 2.4.0.</p> <p>patch for b2_1 <a href="http://review.whamcloud.com/#/c/6754/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#/c/6754/</a></p> Related Development Rank 1|hzvt0v: Rank (Obsolete) 8630