Closed jmesnil closed 5 years ago
Hi @jmesnil. Thanks for your PR.
I'm waiting for a openshift-s2i or openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
/lgtm
/ok-to-test /approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: bparees, jmesnil
The full list of commands accepted by this bot can be found here.
The pull request process is described here
@bparees thanks. When do you plan to push the openshift/wildfly-160-centos7
Docker image with that fix?
@jmesnil normally it happens automatically on merge. It looks like our push job failed and for some reason I did not see a jenkins email from the job. I'll rekick it.
/cc @adambkaplan
new image is up now: https://hub.docker.com/r/openshift/wildfly-160-centos7/tags
thanks!
Use
hostname -i
to determine the IP address of the Pod and bind the WildFly public interface to it.Do not bind jgroups.bind_address to 0.0.0.0 (that is incorrect for JGroups). Instead, if JGroups subsystem is defined, the standalone configuration can attach its socket-binding to the public interface so that the Pod IP addres is properly used to identiy JGroups nodes.