3.0.2.5 update failed - hyper-v problem!

Report bugs and workarounds
Post Reply
liam87
Posts: 4
Joined: 05 Dec 2017 08:38

3.0.2.5 update failed - hyper-v problem!

Post by liam87 » 05 Dec 2017 08:41

Hey there,

I'm trying to update to 3.0.2.5 but I always getting an error on the hyper-v part:
[EFA] Good you are root
[EFA] Starting update to EFA-3.0.2.5
[EFA] Good you are root
Loaded plugins: fastestmirror, security
Setting up Update Process
Loading mirror speeds from cached hostfile
* EFA: dl7.efa-project.org
* base: mirror.infonline.de
* epel: mir01.syntis.net
* extras: centos.mirror.iphh.net
* mariadb: mirror.netcologne.de
* updates: centos.mirror.iphh.net
http://centos.mirror.iphh.net/CentOS/6. ... repomd.xml: [Errno 12] Timeout on http://centos.mirror.iphh.net/CentOS/6. ... repomd.xml: (28, 'Operation too slow. Less than 1 bytes/sec transfered the last 30 seconds')
Trying other mirror.
http://centos.mirror.iphh.net/CentOS/6. ... repomd.xml: [Errno 14] PYCURL ERROR 7 - "Failed to connect to 2001:868:0:182::13: Network is unreachable"
Trying other mirror.
Resolving Dependencies
--> Running transaction check
---> Package kernel.x86_64 0:2.6.32-696.16.1.el6 will be installed
---> Package kernel-devel.x86_64 0:2.6.32-696.16.1.el6 will be installed
---> Package kernel-firmware.noarch 0:2.6.32-696.10.3.el6 will be updated
---> Package kernel-firmware.noarch 0:2.6.32-696.16.1.el6 will be an update
---> Package kernel-headers.x86_64 0:2.6.32-696.10.3.el6 will be updated
---> Package kernel-headers.x86_64 0:2.6.32-696.16.1.el6 will be an update
--> Finished Dependency Resolution
--> Running transaction check
---> Package kernel.x86_64 0:2.6.32-642.15.1.el6 will be erased
--> Processing Dependency: kernel < 2.6.32-643 for package: kmod-microsoft-hyper-v-4.1.2-20160809.x86_64
--> Processing Dependency: kernel(__vmbus_driver_register) = 0xb1b6bc8c for package: kmod-microsoft-hyper-v-4.1.2-20160809.x86_64
--> Processing Dependency: kernel(vmbus_close) = 0x9751d826 for package: kmod-microsoft-hyper-v-4.1.2-20160809.x86_64
--> Processing Dependency: kernel(vmbus_driver_unregister) = 0xd15637a5 for package: kmod-microsoft-hyper-v-4.1.2-20160809.x86_64
--> Processing Dependency: kernel(vmbus_open) = 0xddc5c776 for package: kmod-microsoft-hyper-v-4.1.2-20160809.x86_64
--> Processing Dependency: kernel(vmbus_recvpacket_raw) = 0x4cd23ff4 for package: kmod-microsoft-hyper-v-4.1.2-20160809.x86_64
--> Processing Dependency: kernel(vmbus_sendpacket) = 0x60267c8f for package: kmod-microsoft-hyper-v-4.1.2-20160809.x86_64
--> Processing Dependency: kernel < 2.6.32-643 for package: kmod-microsoft-hyper-v-4.1.2-20160809.x86_64
---> Package kernel-devel.x86_64 0:2.6.32-642.15.1.el6 will be erased
--> Running transaction check
---> Package kernel.x86_64 0:2.6.32-642.15.1.el6 will be erased
---> Package kmod-microsoft-hyper-v.x86_64 0:4.1.2-20160809 will be erased
--> Processing Dependency: microsoft-hyper-v-kmod = 4.1.2 for package: microsoft-hyper-v-4.1.2-20160809.x86_64
--> Running transaction check
---> Package microsoft-hyper-v.x86_64 0:4.1.2-20160809 will be erased
--> Finished Dependency Resolution
Error: Package: kmod-microsoft-hyper-v-4.1.2-20160809.x86_64 (installed)
Requires: kernel < 2.6.32-643
Removing: kernel-2.6.32-642.15.1.el6.x86_64 (@updates)
kernel = 2.6.32-642.15.1.el6
kernel = 2.6.32-642.15.1.el6
Installed: kernel-2.6.32-696.1.1.el6.x86_64 (@updates)
kernel = 2.6.32-696.1.1.el6
kernel = 2.6.32-696.1.1.el6
Installed: kernel-2.6.32-696.3.1.el6.x86_64 (@updates)
kernel = 2.6.32-696.3.1.el6
kernel = 2.6.32-696.3.1.el6
Installed: kernel-2.6.32-696.3.2.el6.x86_64 (@updates)
kernel = 2.6.32-696.3.2.el6
kernel = 2.6.32-696.3.2.el6
Installed: kernel-2.6.32-696.10.3.el6.x86_64 (@updates)
kernel = 2.6.32-696.10.3.el6
kernel = 2.6.32-696.10.3.el6
Available: kernel-2.6.32-696.el6.x86_64 (base)
kernel = 2.6.32-696.el6
kernel = 2.6.32-696.el6
Available: kernel-2.6.32-696.6.3.el6.x86_64 (updates)
kernel = 2.6.32-696.6.3.el6
kernel = 2.6.32-696.6.3.el6
Available: kernel-2.6.32-696.10.1.el6.x86_64 (updates)
kernel = 2.6.32-696.10.1.el6
kernel = 2.6.32-696.10.1.el6
Available: kernel-2.6.32-696.10.2.el6.x86_64 (updates)
kernel = 2.6.32-696.10.2.el6
kernel = 2.6.32-696.10.2.el6
Available: kernel-2.6.32-696.13.2.el6.x86_64 (updates)
kernel = 2.6.32-696.13.2.el6
kernel = 2.6.32-696.13.2.el6
Installing: kernel-2.6.32-696.16.1.el6.x86_64 (updates)
kernel = 2.6.32-696.16.1.el6
kernel = 2.6.32-696.16.1.el6
Available: kernel-debug-2.6.32-696.el6.x86_64 (base)
kernel = 2.6.32-696.el6
Available: kernel-debug-2.6.32-696.1.1.el6.x86_64 (updates)
kernel = 2.6.32-696.1.1.el6
Available: kernel-debug-2.6.32-696.3.1.el6.x86_64 (updates)
kernel = 2.6.32-696.3.1.el6
Available: kernel-debug-2.6.32-696.3.2.el6.x86_64 (updates)
kernel = 2.6.32-696.3.2.el6
Available: kernel-debug-2.6.32-696.6.3.el6.x86_64 (updates)
kernel = 2.6.32-696.6.3.el6
Available: kernel-debug-2.6.32-696.10.1.el6.x86_64 (updates)
kernel = 2.6.32-696.10.1.el6
Available: kernel-debug-2.6.32-696.10.2.el6.x86_64 (updates)
kernel = 2.6.32-696.10.2.el6
Available: kernel-debug-2.6.32-696.10.3.el6.x86_64 (updates)
kernel = 2.6.32-696.10.3.el6
Available: kernel-debug-2.6.32-696.13.2.el6.x86_64 (updates)
kernel = 2.6.32-696.13.2.el6
Available: kernel-debug-2.6.32-696.16.1.el6.x86_64 (updates)
kernel = 2.6.32-696.16.1.el6
You could try using --skip-broken to work around the problem
** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows:
kmod-microsoft-hyper-v-4.2.3.1-20171101.x86_64 is a duplicate with kmod-microsoft-hyper-v-4.1.2-20160809.x86_64
sendmail: warning: /etc/postfix/main.cf, line 764: overriding earlier entry: smtpd_client_restrictions=permit_sasl_authenticated, reject_rbl_client sbl.spamhaus.org, reject_rbl_client cbl.abuseat.org, reject_rbl_client all.spam-rbl.fr, reject_rbl_client bl.spamcop.net, reject_rbl_client relays.mail-abuse.org, reject_rbl_client sbl-xbl.spamhaus.org, reject_rbl_client zen.spamhaus.org, reject_rbl_client b.barracudacentral.org
postdrop: warning: /etc/postfix/main.cf, line 764: overriding earlier entry: smtpd_client_restrictions=permit_sasl_authenticated, reject_rbl_client sbl.spamhaus.org, reject_rbl_client cbl.abuseat.org, reject_rbl_client all.spam-rbl.fr, reject_rbl_client bl.spamcop.net, reject_rbl_client relays.mail-abuse.org, reject_rbl_client sbl-xbl.spamhaus.org, reject_rbl_client zen.spamhaus.org, reject_rbl_client b.barracudacentral.org
Update to Version 3.0.2.4 FAILED. Updates cancelled.
Please visit http://www.efa-project.org for more information.
/var/EFA/update/EFA-update-script died with exit status 1

The question is, can i exclude this part from been checkt because I updated the Linux Integration Service for hyper-v already to 4.2.x so I don't want to downgrade that again.

Thanks for every helpful answer.

best regars

liam87
Posts: 4
Joined: 05 Dec 2017 08:38

Re: 3.0.2.5 update failed - hyper-v problem!

Post by liam87 » 05 Dec 2017 08:46

the ipv6 error can be ignored. already fixed.

User avatar
shawniverson
Posts: 2831
Joined: 13 Jan 2014 23:30
Location: Rushville, Indiana, USA
Contact:

Re: 3.0.2.5 update failed - hyper-v problem!

Post by shawniverson » 05 Dec 2017 11:49

Part of the problem here is that you are going to have to reapply kmod-microsoft-hyper-v anyway because it is a set of kernel modules, and the kernel update is probably going to break it anyway if you exclude it. So I would advise erasing it, upgrading the kernel, and reinstalling it, to make sure it installs the right modules for the updated kernel after restarting.
Version eFa 4.0.0 RC3 now available in testing repo. Come join us in advancing eFa!

liam87
Posts: 4
Joined: 05 Dec 2017 08:38

Re: 3.0.2.5 update failed - hyper-v problem!

Post by liam87 » 05 Dec 2017 16:08

thanks for your answer already :-) Do you have the commands for that? Sorry I'm not a linux pro just started with it^^

liam87
Posts: 4
Joined: 05 Dec 2017 08:38

Re: 3.0.2.5 update failed - hyper-v problem!

Post by liam87 » 06 Dec 2017 07:39

thanks alot. I could uninstall the hyper stuff with the following part:

rpm -e `rpm -qa | grep hyper`

after that the update could be installed and I'm now on 3.0.2.5.

Thanks a lot for your help. Awesome project! :D

Post Reply