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:
The ocf_exit_reason function is a way to provide admin feedback about exactly why a resource failed to start.
In the case of failures of 'docker run', the error is always set to "docker failed to launch container". We can do better :-)
Version-Release number of selected component (if applicable):
resource-agents-3.9.5-105.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Create two container resources with the same port mapping (-p 1234:1234) and arrange for them to start on the same node
Actual results:
pcs status says:
* myContainer_start_0 on myNode 'unknown error' (1): call=16779, status=complete, exitreason='docker failed to launch container',
Expected results:
* myContainer_start_0 on myNode 'unknown error' (1): call=16779, status=complete, exitreason=' Bind for 0.0.0.0:1234 failed: port is already allocated.',
Additional info:
--- docker 2017-11-01 21:50:21.423600738 +1100
+++ docker.beekhof 2017-11-01 21:48:10.570475949 +1100
@@ -301,11 +302,21 @@ docker_start()
# we already know at this point it wouldn't be running
remove_container
ocf_log info "running container $CONTAINER for the first time"
- ocf_run docker run $run_opts $OCF_RESKEY_image $OCF_RESKEY_run_cmd
+ output=`docker run $run_opts $OCF_RESKEY_image $OCF_RESKEY_run_cmd 2>&1`
+ rc=$?
+
+ if [ $rc -ne 0 ]; then
+ reason=`echo $output | sed -e 's@See ./usr/bin.*@@' -e 's@.*Error response from daemon: @@' -e 's@[^\:]*:@@'`
+ ocf_exit_reason "$reason"
+ ocf_log err "$output"
+ ocf_run -info docker ps -a
+ return $OCF_ERR_GENERIC
+ fi
fi
if [ $? -ne 0 ]; then
ocf_exit_reason "docker failed to launch container"
+ ocf_run -info docker ps -a
return $OCF_ERR_GENERIC
fi
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-2018:0757