OpenVZ Forum: Support » yum update issue on CentOS 6.4

Home » General » Support » yum update issue on CentOS 6.4 (yum update issue on CentOS 6.4 ackage kernel-firmware-2.6.32-431.11.2.el6.noarch is obsoleted by vzkernel-firmware-2.6.32-042stab083.2.noarch which is already installed)

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

yum update issue on CentOS 6.4 [message #51306]

Tue, 08 April 2014 22:05

PJF5000
Messages: 5
Registered: January 2013

Junior Member

Hi, I'm attempting to run yum update on a CentOS 6.4 server and it is failing with the following.

Currently running 2.6.32-042stab083.2.

---> Package kernel.x86_64 0:2.6.32-431.11.2.el6 will be installed
--> Processing Dependency: kernel-firmware >= 2.6.32-431.11.2.el6 for package: kernel-2.6.32-431.11.2.el6.x86_64
Package kernel-firmware-2.6.32-431.11.2.el6.noarch is obsoleted by vzkernel-firmware-2.6.32-042stab083.2.noarch which is already installed
--> Finished Dependency Resolution
Error: Package: kernel-2.6.32-431.11.2.el6.x86_64 (updates)
Requires: kernel-firmware >= 2.6.32-431.11.2.el6
Removing: vzkernel-firmware-2.6.32-042stab083.2.noarch (@openvz-kernel-rhel6)
kernel-firmware = 2.6.32-358.23.2.el6
Updated By: vzkernel-firmware-2.6.32-042stab085.20.noarch (openvz-kernel-rhel6)
kernel-firmware = 2.6.32-431.1.2.el6
Available: kernel-firmware-2.6.32-431.el6.noarch (base)
kernel-firmware = 2.6.32-431.el6
Available: kernel-firmware-2.6.32-431.1.2.0.1.el6.noarch (updates)
kernel-firmware = 2.6.32-431.1.2.0.1.el6
Available: kernel-firmware-2.6.32-431.3.1.el6.noarch (updates)
kernel-firmware = 2.6.32-431.3.1.el6
Available: kernel-firmware-2.6.32-431.5.1.el6.noarch (updates)
kernel-firmware = 2.6.32-431.5.1.el6
Available: kernel-firmware-2.6.32-431.11.2.el6.noarch (updates)
kernel-firmware = 2.6.32-431.11.2.el6
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

Here is the complete output of yum update:

"
yum update
Loaded plugins: dellsysid, fastestmirror, security
Determining fastest mirrors
* openvz-kernel-rhel6: mirror.scalabledns.com
* openvz-utils: mirror.scalabledns.com
base | 3.7 kB 00:00
base/primary_db | 4.4 MB 00:00
extras | 3.4 kB 00:00
extras/primary_db | 19 kB 00:00
ksplice-uptrack | 951 B 00:00
ksplice-uptrack/primary | 4.2 kB 00:00
ksplice-uptrack 14/14
openvz-kernel-rhel6 | 951 B 00:00
openvz-kernel-rhel6/primary | 3.5 kB 00:00
openvz-kernel-rhel6 12/12
openvz-utils | 951 B 00:00
openvz-utils/primary | 9.2 kB 00:00
openvz-utils 38/38
r1soft | 951 B 00:00
r1soft/primary | 19 kB 00:00
r1soft 18/18
updates | 3.4 kB 00:00
updates/primary_db | 2.6 MB 00:00
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package abrt.x86_64 0:2.0.8-16.el6.centos.1 will be updated
---> Package abrt.x86_64 0:2.0.8-21.el6.centos will be an update
---> Package abrt-addon-ccpp.x86_64 0:2.0.8-16.el6.centos.1 will be updated
---> Package abrt-addon-ccpp.x86_64 0:2.0.8-21.el6.centos will be an update
---> Package abrt-addon-kerneloops.x86_64 0:2.0.8-16.el6.centos.1 will be updated
---> Package abrt-addon-kerneloops.x86_64 0:2.0.8-21.el6.centos will be an update
---> Package abrt-addon-python.x86_64 0:2.0.8-16.el6.centos.1 will be updated
---> Package abrt-addon-python.x86_64 0:2.0.8-21.el6.centos will be an update
---> Package abrt-cli.x86_64 0:2.0.8-16.el6.centos.1 will be updated
---> Package abrt-cli.x86_64 0:2.0.8-21.el6.centos will be an update
---> Package abrt-libs.x86_64 0:2.0.8-16.el6.centos.1 will be updated
---> Package abrt-libs.x86_64 0:2.0.8-21.el6.centos will be an update
---> Package abrt-tui.x86_64 0:2.0.8-16.el6.centos.1 will be updated
---> Package abrt-tui.x86_64 0:2.0.8-21.el6.centos will be an update
---> Package atk.x86_64 0:1.28.0-2.el6 will be updated
---> Package atk.x86_64 0:1.30.0-1.el6 will be an update
---> Package autofs.x86_64 1:5.0.5-75.el6_4 will be updated
---> Package autofs.x86_64 1:5.0.5-89.el6_5.1 will be an update
---> Package bfa-firmware.noarch 0:3.0.3.1-1.el6 will be updated
---> Package bfa-firmware.noarch 0:3.2.21.1-2.el6 will be an update
---> Package bind-libs.x86_64 32:9.8.2-0.17.rc1.el6_4.6 will be updated
---> Package bind-libs.x86_64 32:9.8.2-0.23.rc1.el6_5.1 will be an update
---> Package bind-utils.x86_64 32:9.8.2-0.17.rc1.el6_4.6 will be updated
---> Package bind-utils.x86_64 32:9.8.2-0.23.rc1.el6_5.1 will be an update
---> Package biosdevname.x86_64 0:0.4.1-3.el6 will be updated
---> Package biosdevname.x86_64 0:0.5.0-2.el6 will be an update
---> Package boost.x86_64 0:1.41.0-17.el6_4 will be updated
---> Package boost.x86_64 0:1.41.0-18.el6 will be an update
---> Package boost-date-time.x86_64 0:1.41.0-17.el6_4 will be updated
---> Package boost-date-time.x86_64 0:1.41.0-18.el6 will be an update
---> Package boost-filesystem.x86_64 0:1.41.0-17.el6_4 will be updated
---> Package boost-filesystem.x86_64 0:1.41.0-18.el6 will be an update
---> Package boost-graph.x86_64 0:1.41.0-17.el6_4 will be updated
---> Package boost-graph.x86_64 0:1.41.0-18.el6 will be an update
---> Package boost-iostreams.x86_64 0:1.41.0-17.el6_4 will be updated
---> Package boost-iostreams.x86_64 0:1.41.0-18.el6 will be an update
---> Package boost-program-options.x86_64 0:1.41.0-17.el6_4 will be updated
---> Package boost-program-options.x86_64 0:1.41.0-18.el6 will be an update
---> Package boost-python.x86_64 0:1.41.0-17.el6_4 will be updated
---> Package boost-python.x86_64 0:1.41.0-18.el6 will be an update
---> Package boost-regex.x86_64 0:1.41.0-17.el6_4 will be updated
---> Package boost-regex.x86_64 0:1.41.0-18.el6 will be an update
---> Package boost-serialization.x86_64 0:1.41.0-17.el6_4 will be updated
---> Package boost-serialization.x86_64 0:1.41.0-18.el6 will be an update
---> Package boost-signals.x86_64 0:1.41.0-17.el6_4 will be updated
---> Package boost-signals.x86_64 0:1.41.0-18.el6 will be an update
---> Package boost-system.x86_64 0:1.41.0-17.el6_4 will be updated
---> Package boost-system.x86_64 0:1.41.0-18.el6 will be an update
---> Package boost-test.x86_64 0:1.41.0-17.el6_4 will be updated
---> Package boost-test.x86_64 0:1.41.0-18.el6 will be an update
---> Package boost-thread.x86_64 0:1.41.0-17.el6_4 will be updated
---> Package boost-thread.x86_64 0:1.41.0-18.el6 will be an update
---> Package boost-wave.x86_64 0:1.41.0-17.el6_4 will be updated
---> Package boost-wave.x86_64 0:1.41.0-18.el6 will be an update
---> Package btparser.x86_64 0:0.17-1.el6 will be updated
---> Package btparser.x86_64 0:0.17-2.el6 will be an update
---> Package busybox.x86_64 1:1.15.1-16.el6_4 will be updated
---> Package busybox.x86_64 1:1.15.1-20.el6 will be an update
---> Package ca-certificates.noarch 0:2010.63-3.el6_1.5 will be updated
---> Package ca-certificates.noarch 0:2013.1.95-65.1.el6_5 will be an update
--> Processing Dependency: p11-kit-trust >= 0.18.4-2 for package: ca-certificates-2013.1.95-65.1.el6_5.noarch
--> Processing Dependency: p11-kit >= 0.18.4-2 for package: ca-certificates- ...

[ Show the rest of the message ]

Report message to a moderator

Re: yum update issue on CentOS 6.4 [message #51312 is a reply to message #51306]

Thu, 10 April 2014 18:45

Paparaciz
Messages: 302
Registered: August 2009

Senior Member

replied many times- please search in wiki and forums.

Report message to a moderator

Re: yum update issue on CentOS 6.4 [message #51314 is a reply to message #51312]

Thu, 10 April 2014 19:08

PJF5000
Messages: 5
Registered: January 2013

Junior Member

You are correct, it was an easy and obvious fix.
I searched before but it was a long day and my brain was tired.

The fix was in: /etc/yum.repos.d/CentOS-Base.repo

I added

exclude=kernel*

Under the [base] and [updates] repos.

I've done this a million times, must have missed the obvious here.

Sorry for the lame post!

Thanks for your help.

Report message to a moderator

Re: yum update issue on CentOS 6.4 [message #51315 is a reply to message #51306]

Thu, 10 April 2014 19:20

Paparaciz
Messages: 302
Registered: August 2009

Senior Member

no, the right sollution is:

https://wiki.openvz.org/Vzkernel-firmware

Report message to a moderator

Re: yum update issue on CentOS 6.4 [message #51317 is a reply to message #51306]

Thu, 10 April 2014 20:15

Ales
Messages: 330
Registered: May 2009

Senior Member

I've been running our systems without stock kernel, with just vzkernel and using vzkernel-firmware.

The added benefit is less updates and we don't need to double check if the stock kernel has set itself as default in grub.conf. For us, this approach has worked well for years... YMMV, of course.

Report message to a moderator

Re: yum update issue on CentOS 6.4 [message #51318 is a reply to message #51317]

Thu, 10 April 2014 20:57

PJF5000
Messages: 5
Registered: January 2013

Junior Member

Ales,

Thatis how I normally run them as well.

Why would I keep the stock CentOS kernels and kernel-firmware installed if I am only running OpenVZ and will never be booting back into the stock CentOS kernel.

My solution was to remove the CentOS kernels, and exlcude them from the update repo.

Paparaciz, is there a reason why this isn't the correct solution?

Thanks for your help.

Report message to a moderator

Re: yum update issue on CentOS 6.4 [message #51319 is a reply to message #51306]

Thu, 10 April 2014 21:24

Paparaciz
Messages: 302
Registered: August 2009

Senior Member

personally I also tend to remove stock kernel, but as a matter of my answer- it is only quick reply for people which didn't/don't want to remove stock kernel.
Also there can be situations when you debug problems, and in process you install stock kernel (to verify is this openvz specific problem or general problem), than you can also get this situation.

and...
in fact if I remember everything ok, there was some situations when it still goes to dependency hell. after that this wiki article came in.
Also keep in mind that openvz kernel is some time behind of stock kernel, so stock kernel-firmware package can have fixes or improovements that still not available in openvz vzkernel-firmware package.

thats my opinion, and thus I remove stock kernel, but setup as in wiki article.

Report message to a moderator

Previous Topic:	IPs stop working
Next Topic:	Unable to enter VE

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Thu May 02 12:56:36 GMT 2024

Total time taken to generate the page: 0.01896 seconds