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.
Above patch is wrong. How can you check for value of variable without initializing it. (docker-latest_devmapper_meta_dir)
We have following
DOCKER_METADATA_DIR="/var/lib/docker"
We have to make sure that for docker-latest package it is changed to.
DOCKER_METADATA_DIR="/var/lib/docker-latest"
In docker-latest-1.10.3-40.el7.x86_64
#cat /etc/sysconfig/docker-latest-storage-setup
DEVS=/dev/vdb
VG=docker-latest-test
WIPE_SIGNATURES=true
# docker-latest-storage-setup
INFO: Volume group backing root filesystem could not be determined
INFO: Device /dev/vdb is already partitioned and is part of volume group docker-latest-test
Rounding up size to full physical extent 12.00 MiB
Logical volume "docker-latest-poolmeta" created.
Logical volume "docker-latest-pool" created.
WARNING: Converting logical volume docker-latest-test/docker-latest-pool and docker-latest-test/docker-latest-poolmeta to pool's data and metadata volumes.
THIS WILL DESTROY CONTENT OF LOGICAL VOLUME (filesystem etc.)
Converted docker-latest-test/docker-latest-pool to thin pool.
Logical volume "docker-latest-pool" changed.
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://access.redhat.com/errata/RHBA-2016:1275