Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

Starting from a Red Hat docker 1.10.3 system configured for devicemapper graph driver storage, running a yum update to 1.12.2-5.el7 results in a systemd service definition which no longer points to, or migrates, the existing /etc/sysconfig/docker-storage environment file which contains the docker storage options required to successfully start the docker service/daemon after the upgrade.

The user must currently manually re-add /etc/sysconfig/docker-storage to the service file (or copy the storage options to /etc/sysconfig/docker)

If this is not done, the docker service will not start


Version-Release number of selected component (if applicable):  docker 1.12.2-5.el7

How reproducible: always


Steps to Reproduce:
1.  Install red hat docker 1.10.3
2.  Configure for devicemapper storage with docker-storage-setup.  Verify with docker info
3.  Install 1.12.2-5 with yum update docker docker-common docker-selinux docker-rhel-push-plugin
4.  systemctl start docker

Actual results:

Docker fails to start - docker-storage configuration is not active in the systemd service file

Expected results:


Docker starts with pre-existing storage configuration active

The following lines in the "before" docker.service file

EnvironmentFile=-/etc/sysconfig/docker
EnvironmentFile=-/etc/sysconfig/docker-storage
EnvironmentFile=-/etc/sysconfig/docker-network


become this in the "after" file:

EnvironmentFile=-/etc/sysconfig/docker
EnvironmentFile=-/etc/sysconfig/docker
EnvironmentFile=-/etc/sysconfig/docker

Live update from 1.10.3 to 1.12.3-4, the docker service is always alive, move to verified

# cat /etc/sysconfig/docker-storage-setup 
WIPE_SIGNATURES=true
DEVS=/dev/sdb
VG=docker-test

# docker info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 0
Server Version: 1.10.3
Storage Driver: devicemapper
 Pool Name: docker--test-docker--pool

#yum update
....
# docker info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 0
Server Version: 1.12.3
Storage Driver: devicemapper
 Pool Name: docker--test-docker--pool

*** Bug 1395721 has been marked as a duplicate of this bug. ***

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2017-0116.html