Yum update failed
-
No issue for me.
-
Isn't this the second time you have had issues with yum? I believe I have had this before and iirc I had to make sure my kernel was up to date. Don't hold me to that.
-
@jaredbusch said in Yum update failed:
kernel-3.10.0-862.2.3.el7.x86_64 requires linux-firmware >= 20180113-61
The Google says you are the first person to have this issue
Congrats.
-
Back at my desk now, I rebooted the instance first and then manually ran
yum update.[jbusch@bna-nc ~]$ sudo yum update [sudo] password for jbusch: Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: centos.unixheads.org * epel: mirror.oss.ou.edu * extras: mirror.cs.uwp.edu * remi-php71: repo1.dal.innoscale.net * remi-safe: repo1.dal.innoscale.net * updates: distro.ibiblio.org Resolving Dependencies --> Running transaction check ---> Package kernel.x86_64 0:3.10.0-862.2.3.el7 will be installed --> Processing Dependency: linux-firmware >= 20180113-61 for package: kernel-3.10.0-862.2.3.el7.x86_64 ---> Package kernel-tools.x86_64 0:3.10.0-693.21.1.el7 will be updated ---> Package kernel-tools.x86_64 0:3.10.0-862.2.3.el7 will be an update ---> Package kernel-tools-libs.x86_64 0:3.10.0-693.21.1.el7 will be updated ---> Package kernel-tools-libs.x86_64 0:3.10.0-862.2.3.el7 will be an update ---> Package krb5-libs.x86_64 0:1.15.1-8.el7 will be updated ---> Package krb5-libs.x86_64 0:1.15.1-19.el7 will be an update ---> Package python-perf.x86_64 0:3.10.0-693.21.1.el7 will be updated ---> Package python-perf.x86_64 0:3.10.0-862.2.3.el7 will be an update ---> Package selinux-policy.noarch 0:3.13.1-166.el7_4.9 will be updated ---> Package selinux-policy.noarch 0:3.13.1-192.el7_5.3 will be an update --> Processing Dependency: policycoreutils >= 2.5-18 for package: selinux-policy-3.13.1-192.el7_5.3.noarch ---> Package selinux-policy-targeted.noarch 0:3.13.1-166.el7_4.9 will be updated ---> Package selinux-policy-targeted.noarch 0:3.13.1-192.el7_5.3 will be an update --> Processing Dependency: policycoreutils >= 2.5-18 for package: selinux-policy-targeted-3.13.1-192.el7_5.3.noarch ---> Package tzdata.noarch 0:2018d-1.el7 will be updated ---> Package tzdata.noarch 0:2018e-3.el7 will be an update --> Finished Dependency Resolution --> Running transaction check ---> Package kernel.x86_64 0:3.10.0-693.5.2.el7 will be erased ---> Package kernel.x86_64 0:3.10.0-862.2.3.el7 will be installed --> Processing Dependency: linux-firmware >= 20180113-61 for package: kernel-3.10.0-862.2.3.el7.x86_64 ---> Package selinux-policy.noarch 0:3.13.1-192.el7_5.3 will be an update --> Processing Dependency: policycoreutils >= 2.5-18 for package: selinux-policy-3.13.1-192.el7_5.3.noarch ---> Package selinux-policy-targeted.noarch 0:3.13.1-192.el7_5.3 will be an update --> Processing Dependency: policycoreutils >= 2.5-18 for package: selinux-policy-targeted-3.13.1-192.el7_5.3.noarch --> Finished Dependency Resolution Error: Package: selinux-policy-3.13.1-192.el7_5.3.noarch (updates) Requires: policycoreutils >= 2.5-18 Installed: policycoreutils-2.5-17.1.el7.x86_64 (@base) policycoreutils = 2.5-17.1.el7 Error: Package: selinux-policy-targeted-3.13.1-192.el7_5.3.noarch (updates) Requires: policycoreutils >= 2.5-18 Installed: policycoreutils-2.5-17.1.el7.x86_64 (@base) policycoreutils = 2.5-17.1.el7 Error: Package: kernel-3.10.0-862.2.3.el7.x86_64 (updates) Requires: linux-firmware >= 20180113-61 Installed: linux-firmware-20170606-58.gitc990aae.el7_4.noarch (@updates) linux-firmware = 20170606-58.gitc990aae.el7_4 Available: linux-firmware-20170606-56.gitc990aae.el7.noarch (base) linux-firmware = 20170606-56.gitc990aae.el7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest -
@scottalanmiller said in Yum update failed:
kernel-3.10.0-862.2.3.el7.x86_64 requires linux-firmware >= 20180113-61
Grr...
-
Have you tried getting linux-firmware manually and installing it first?
https://pkgs.org/download/linux-firmware
or
https://centos.pkgs.org/7/centos-x86_64/linux-firmware-20180220-62.git6d51311.el7.noarch.rpm.html -
I was able to correct this on a few of my instances that were having issues by running:
yum clean all
rm -rf /var/cache/yumand then attempting the update again.
I think the cause of this was initially having a network connectivity issue on my end, so this may not help everyone, but worth a shot?
-
@baslugger48 said in Yum update failed:
I was able to correct this on a few of my instances that were having issues by running:
yum clean all
rm -rf /var/cache/yumand then attempting the update again.
I think the cause of this was initially having a network connectivity issue on my end, so this may not help everyone, but worth a shot?
I did that this morning right after I posted. Same result.
Then I did
--skip-broken.I just did it again and now there are 230 updates and no conflicts.
-
Dependencies Resolved ================================================================================================================================== Package Arch Version Repository Size ================================================================================================================================== Updating: kernel-tools x86_64 3.10.0-862.2.3.el7 updates 6.2 M kernel-tools-libs x86_64 3.10.0-862.2.3.el7 updates 6.1 M krb5-libs x86_64 1.15.1-19.el7 updates 747 k python-perf x86_64 3.10.0-862.2.3.el7 updates 6.2 M tzdata noarch 2018e-3.el7 updates 482 k Skipped (dependency problems): kernel x86_64 3.10.0-862.2.3.el7 updates 46 M selinux-policy noarch 3.13.1-192.el7_5.3 updates 453 k selinux-policy-targeted noarch 3.13.1-192.el7_5.3 updates 6.6 M Transaction Summary ================================================================================================================================== Upgrade 5 Packages Skipped (dependency problems) 3 Packages Total download size: 20 M Is this ok [y/d/N]: y Downloading packages: Delta RPMs disabled because /usr/bin/applydeltarpm not installed. -
-
I have 4 CentOS 7 servers at this location that I want to migrate to Fedora, just not high on my priority list.
-
@jaredbusch said in Yum update failed:
I have 4 CentOS 7 servers at this location that I want to migrate to Fedora, just not high on my priority list.
But a little higher on that list now
I truly find fedora updates more reliable than CentOS ones.
-
Can you upgrade to policycoreutils >= 2.5-18?
-
@obsolesce it ran this afternoon. I noted that.
