Correct. On Sat., 19 Nov. 2016 at 12:29 am, Marko Lukša <marko.lu...@gmail.com> wrote:
> Hi, > > so clustering is working, but you still see the warning in the log? If so, > we'd like to fix this. > > I'm assuming you're setting the HTTP_PROXY environment variable? As you've > pointed out, since we're calling curl without --no-proxy, it can't access > the API server. The actual kube-ping code, on the other hand, can access it > because it bypasses the proxy. > > M. > > > On 18. 11. 2016 02:32, Lionel Orellana wrote: > > I deployed a distributable war and got the output I was looking for. All > good with the world. Thanks. > > On 18 November 2016 at 08:29, Lionel Orellana <lione...@gmail.com> wrote: > > But I can't tell if the second replica joined the cluster created by the > first. > > I'm expecting to see "Number of cluster members: x" in the logs but it's > not showing in any of the two instances. > > On 17 November 2016 at 22:55, Lionel Orellana <lione...@gmail.com> wrote: > > Thanks Frederick. I have done that. > > On Thu., 17 Nov. 2016 at 10:48 pm, Frederic Giloux <fgil...@redhat.com> > wrote: > > Hi Lionel, > > JBoss on OpenShift uses JGroups Kube_ping to discover the other members of > the cluster. This actually calls the Kubernetes REST API. Therefore you > need to have the proper rights allocated to your service account. More > information here: > https://access.redhat.com/documentation/en/red-hat-xpaas/0/single/red-hat-xpaas-eap-image/#clustering > > Best Regards, > > Frédéric > > > On Thu, Nov 17, 2016 at 11:58 AM, Lionel Orellana <lione...@gmail.com> > wrote: > > Hi, > > I'm trying to run Jboss cluster using the eap64-basic-s2i v1.3.2 template > on Origin 1.3. > > The application built and deployed fined. The second one started fine but > I can't tell if it joined the existing cluster. I was expecting to see an > output along the lines of "number of members in the cluster: 2" which I > have seen in the past with Jboss. > > There is a warning at the begining of the startup logs: > > "WARNING: Service account unable to test permissions to view pods in > kubernetes (HTTP 000). Clustering will be unavailable. Please refer to the > documentation for configuration." > > But looking at the ha.sh launch script this is just > the check_view_pods_permission function using curl without --no-proxy. As > far as I can tell this doesn't affect anything. > > So what do I need to look for to confirm that the second instance joined > the cluster correctly? I am concerned that the proxy might be getting in > the way somewhere else. > > Thanks > > Lionel > > _______________________________________________ > users mailing list > users@lists.openshift.redhat.com > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > > > > > -- > *Frédéric Giloux* > Senior Middleware Consultant > > Red Hat GmbH > MesseTurm, Friedrich-Ebert-Anlage 49, 60308 Frankfurt am Main > > Mobile: +49 (0) 174 1724661 <callto:00491741724661> > E-Mail: fgil...@redhat.com, http://www.redhat.de/ > > Delivering value year after year > Red Hat ranks # 1 in value among software vendors > http://www.redhat.com/promo/vendor/ > > Freedom...Courage...Commitment...Accountability > ________________________________________________________________________ > Red Hat GmbH, http://www.de.redhat.com/ Sitz: Grasbrunn, > Handelsregister: Amtsgericht München, HRB 153243 > Geschäftsführer: Paul Argiry, Charles Cachera, Michael Cunningham, Michael > O'Neill > > > > > > _______________________________________________ > users mailing > listusers@lists.openshift.redhat.comhttp://lists.openshift.redhat.com/openshiftmm/listinfo/users > > > _______________________________________________ > users mailing list > users@lists.openshift.redhat.com > http://lists.openshift.redhat.com/openshiftmm/listinfo/users >
_______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
