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:

On rhel, growpart is not available. Right now docker-storage-setup is written
in such a way that it checks for presence of growpart and if does not exist it
continues.

But current code exits as soon as it sees growpart is not available.

[ -x "/usr/bin/growpart" ] || return

I think it is because of presence of "set -e" option in the script and it
is treated as error.

We need to return 0 so that script continues.

[ -x "/usr/bin/growpart" ] || return 0

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Vivek have you got an updated version?

Dan, this got fixed upstream as well as fix is available in docker-1.6.2-5.el7

In docker-1.6.2-10.el7.x86_64,
without the fix, it will looks like
# docker-storage-setup 
  Volume group "sda3" not found
  Cannot process volume group sda3

after the patch, the script can continue
# docker-storage-setup 
  Volume group "sda3" not found
  Cannot process volume group sda3
  Metadata volume docker-poolmeta already exists. Not creating a new one.

Move to verified.

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