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-5479 Lustre <p>default RH kernel-firmware is noarch but we build ours with x86_64. This results in yum install failure</p> LU-5479

lustre build kernel-firmware should be noarch

Bug Critical Resolved Cannot Reproduce Minh Diep Minh Diep Tue, 12 Aug 2014 20:44:31 +0000 Wed, 20 Nov 2019 18:54:42 +0000 Wed, 20 Nov 2019 18:54:42 +0000 0 7 <p> yum install kernel-2.6.32-431.20.5.el6_lustre kernel-devel-2.6.32-431.20.5.el6_lustre kernel-firmware-2.6.32-431.20.5.el6_lustre kernel-headers-2.6.32-431.20.5.el6_lustre<br/> Loaded plugins: product-id, refresh-packagekit, security, versionlock<br/> Setting up Install Process<br/> Package matching kernel-headers-2.6.32-431.20.5.el6_lustre.x86_64 already installed. Checking for update.<br/> Resolving Dependencies<br/> --&gt; Running transaction check<br/> ---&gt; Package kernel.x86_64 0:2.6.32-431.20.5.el6_lustre will be installed<br/> ---&gt; Package kernel-devel.x86_64 0:2.6.32-431.20.5.el6_lustre will be installed<br/> ---&gt; Package kernel-firmware.x86_64 0:2.6.32-431.20.5.el6_lustre will be installed<br/> ---&gt; Package kernel-headers.x86_64 0:2.6.32-431.17.1.el6_lustre will be updated<br/> ---&gt; Package kernel-headers.x86_64 0:2.6.32-431.20.5.el6_lustre will be an update<br/> --&gt; Finished Dependency Resolution<br/> --&gt; Running transaction check<br/> ---&gt; Package kernel.x86_64 0:2.6.32-431.5.1.el6 will be erased<br/> ---&gt; Package kernel-devel.x86_64 0:2.6.32-431.5.1.el6 will be erased<br/> --&gt; Finished Dependency Resolution<br/> Error: Multilib version problems found. This often means that the root<br/> cause is something else and multilib version checking is just<br/> pointing out that there is a problem. Eg.:<br/> 1. You have an upgrade for kernel-firmware which is missing some<br/> dependency that another package requires. Yum is trying to<br/> solve this by installing an older version of kernel-firmware of the<br/> different architecture. If you exclude the bad architecture<br/> yum will tell you what the root cause is (which package<br/> requires what). You can try redoing the upgrade with<br/> --exclude kernel-firmware.otherarch ... this should give you an error<br/> message showing the root cause of the problem.<br/> 2. You have multiple architectures of kernel-firmware installed, but<br/> yum can only see an upgrade for one of those arcitectures.<br/> If you don't want/need both architectures anymore then you<br/> can remove the one with the missing update and everything<br/> will work.<br/> 3. You have duplicate versions of kernel-firmware installed already.<br/> You can use "yum check" to get yum show these errors.<br/> ...you can also use --setopt=protected_multilib=false to remove<br/> this checking, however this is almost never the correct thing to<br/> do as something else is very likely to go wrong (often causing<br/> much more problems).<br/> Protected multilib versions: kernel-firmware-2.6.32-431.20.5.el6_lustre.x86_64 != kernel-firmware-2.6.32-431.20.3.el6.noarch<br/> You could try using --skip-broken to work around the problem<br/> You could try running: rpm -Va --nofiles --nodigest</p> <p>Minh, are you planning to work on a patch for this problem?</p> <p>I suggest not building the firmware package.<br/> The kernel package should Require: the distro firmware package the kernel is based on.</p> <p>As our patches do not affect their contents, there is no reason to build the headers or perf packages, either.</p> <p>we no longer build kernel-firmware</p> Related Development Rank 1|hzwtlr: Rank (Obsolete) 15285 Severity