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:
docker-storage-setup.sh requires minimum lvm2 version to be lvm2-2.02.112. Express this dependency in spec file when we ship it in 7.1.3.
Running docker-storage-setup.sh with old lvm2 creates bad thin pool mappings
which can't even be removed using latest lvm2 tools in 7.1.
So it will not be wise to get customers into such situation.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Dan mentioned that docker-storage-setup will be shippped in 7.1.3. This fix should go out with it. We don't want existing customers to be running old lvm2
with docker-storage-setup and run into bunch of problems (as we did this morning when a developer from rel-eng tried to setup lvm thin pool).
Docker no longer requires lvm2 since 1.6.2-5 although it should.
In commit edc795d6e3dbd5c9ba09509a437c873347cf2425 docker-storage-setup subpackage was removed together with:
Requires: lvm2 >= 2.02.112
Requires: systemd-units
Requires: xfsprogs
These should be added to the docker package.
(In reply to Michal Minar from comment #5)
> Docker no longer requires lvm2 since 1.6.2-5 although it should.
> In commit edc795d6e3dbd5c9ba09509a437c873347cf2425 docker-storage-setup
> subpackage was removed together with:
>
> Requires: lvm2 >= 2.02.112
> Requires: systemd-units
> Requires: xfsprogs
just to note, systemd-units is provided by the base systemd package itself and the dep list contains a simple 'systemd' (in addition to the other deps mentioned of course)
In docker-1.6.2-10.el7.x86_64, move to verified
# rpm -e lvm2-2.02.115-3.el7.x86_64
lvm2 >= 2.02.112 is needed by (installed) docker-1.6.2-10.el7.x86_64
# rpm -e xfsprogs
xfsprogs is needed by (installed) docker-1.6.2-10.el7.x86_64
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/RHBA-2015-1167.html