Upgrade from 6.0 to 6.1 Fails because of device-mapper version

[Fraser Morehouse]

When performing an upgrade from 6.0 to 6.1 the install failed because once docker was upgraded to 1.5, the dependency on an upgraded device-mapper was not met. There was no indication within the fuel_upgrade.log file explaining the issue.

2015-07-12 02:43:59 DEBUG 2264 (utils) time="2015-07-12T02:43:59Z" level="fatal" msg="Cannot connect to the Docker daemon. Is 'docker
 -d' running on this host?"

When you ran docker -d the follow output was received.

[root@fuel-enoc ~]# docker -d
INFO[0000] +job serveapi(unix:///var/run/docker.sock)
INFO[0000] WARNING: You are running linux kernel version 2.6.32-504.1.3.el6.x86_64, which might be unstable running docker. Please upgrade your kernel to 3.8.0.
INFO[0000] Listening for HTTP on unix (/var/run/docker.sock)
docker: relocation error: docker: symbol dm_task_get_info_with_deferred_remove, version Base not defined in file libdevmapper.so.1.02 with link time reference

This the version in the yum repo provided, and a yum update had been run as well.

[root@fuel-enoc ~]# yum info device-mapper
Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
 * epel: mirror.us.leaseweb.net
Installed Packages
Name : device-mapper
Arch : x86_64
Version : 1.02.79
Release : 8.el6
Size : 173 k
Repo : installed
From repo : anaconda-CentOS-201410241409.x86_64
Summary : Device mapper utility
URL : http://sources.redhat.com/dm
License : GPLv2
Description : This package contains the supporting userspace utility, dmsetup,
            : for the kernel device-mapper.

After following the commands listed here, docker would once again start up.

https://forums.docker.com/t/upgrading-docker-to-current-version-on-centos/340/18

[Bogdan Dobrelya (bogdando)]

Could you please elaborate the steps for a workaround?

[Fraser Morehouse (fraser-morehouse)]

I added the correct device-mapper version through adding an additional repo.

device-mapper-1.02.90-2.el6_6.1.x86_64

[Matthew Mosesohn (raytrac3r)]

It looks like you enabled EPEL on your Fuel Master and that broke the Fuel upgrade scripts. There are newer docker-io packages in EPEL, but device-mapper is located in base CentOS repositories.

For the best results, you should not enable any 3rd party repositories because we can't guarantee compatibility.

[Fraser Morehouse (fraser-morehouse)]

If you actually read what i said, i ONLY did that so that docker would start again. The upgrade script would NOT move forward with the standard EPEL setup.