Geode unit tests completed in 'develop/FlakyTest' with non-zero exit code

[apachegeodeci]

Pipeline results can be found at:

Concourse: 
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/FlakyTest/builds/99

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #954 was SUCCESSFUL (with 2419 tests)

[Spring CI]

---
Spring Data GemFire > Nightly-ApacheGeode > #954 was successful.
---
Scheduled
2421 tests in total.

https://build.spring.io/browse/SGF-NAG-954/





--
This message is automatically generated by Atlassian Bamboo

Geode unit tests completed in 'develop/DistributedTest' with non-zero exit code

[apachegeodeci]

Pipeline results can be found at:

Concourse: 
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/73

Geode unit tests completed in 'develop/FlakyTest' with non-zero exit code

[apachegeodeci]

Pipeline results can be found at:

Concourse: 
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/FlakyTest/builds/98

Build failed in Jenkins: Geode-nightly #1230

[Apache Jenkins Server]

See 


Changes:

[mdodge] GEODE-4791: Enable gradle 4.8 for features and futureproofing (#2050)

[dbarnes] GEODE-5313: User Guide - consolidate transaction coding examples -

[jinmeiliao] GEODE-5284: Add testing surrounding MBean persistence during member

[gesterzhou] Introduces Serializable Consumer for Cluster junit (#2067)

[github] GEODE-5285: Make PdxInstanceImplTest a unit test instead of an

[jdeppe] GEODE-5330: only create one temp folder (#2068)

[jdeppe] Fix test failure related to #2067

--
[...truncated 49.92 KB...]
> Task :geode-connectors:checkMissedTests
> Task :geode-connectors:spotlessJava
> Task :geode-connectors:spotlessJavaCheck
> Task :geode-connectors:spotlessCheck
> Task :geode-connectors:test
> Task :geode-core:assemble
> Task :geode-core:checkMissedTests
> Task :geode-core:spotlessJava
> Task :geode-core:spotlessJavaCheck
> Task :geode-core:spotlessCheck
> Task :geode-core:test
> Task :geode-cq:assemble

> Task :geode-cq:compileTestJava
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

> Task :geode-cq:processTestResources
> Task :geode-cq:testClasses
> Task :geode-cq:checkMissedTests
> Task :geode-cq:spotlessJava
> Task :geode-cq:spotlessJavaCheck
> Task :geode-cq:spotlessCheck
> Task :geode-cq:test
> Task :geode-experimental-driver:jar
> Task :geode-experimental-driver:javadoc
> Task :geode-experimental-driver:javadocJar
> Task :geode-experimental-driver:sourcesJar
> Task :geode-experimental-driver:signArchives SKIPPED
> Task :geode-experimental-driver:assemble

> Task :geode-experimental-driver:compileTestJava
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

> Task :geode-experimental-driver:processTestResources
> Task :geode-experimental-driver:testClasses
> Task :geode-experimental-driver:checkMissedTests
> Task :geode-experimental-driver:spotlessJava
> Task :geode-experimental-driver:spotlessJavaCheck
> Task :geode-experimental-driver:spotlessCheck
> Task :geode-experimental-driver:test
> Task :geode-json:assemble
> Task :geode-json:compileTestJava NO-SOURCE
> Task :geode-json:processTestResources
> Task :geode-json:testClasses
> Task :geode-json:checkMissedTests NO-SOURCE
> Task :geode-json:spotlessJava
> Task :geode-json:spotlessJavaCheck
> Task :geode-json:spotlessCheck
> Task :geode-json:test NO-SOURCE
> Task :geode-old-versions:javadoc
> Task :geode-junit:javadoc
> Task :geode-junit:javadocJar
> Task :geode-junit:sourcesJar
> Task :geode-junit:signArchives SKIPPED
> Task :geode-junit:assemble

> Task :geode-junit:compileTestJava
Note: 

 uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: 

 uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

> Task :geode-junit:processTestResources
> Task :geode-junit:testClasses
> Task :geode-junit:checkMissedTests
> Task :geode-junit:spotlessJava
> Task :geode-junit:spotlessJavaCheck
> Task :geode-junit:spotlessCheck
> Task :geode-junit:test
> Task :geode-lucene:assemble

> Task :geode-lucene:compileTestJava
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

> Task :geode-lucene:processTestResources
> Task :geode-lucene:testClasses
> Task :geode-lucene:checkMissedTests
> Task :geode-lucene:spotlessJava
> Task :geode-lucene:spotlessJavaCheck
> Task :geode-lucene:spotlessCheck
> Task :geode-lucene:test
> Task :geode-old-client-support:assemble
> Task :geode-old-client-support:compileTestJava
> Task :geode-old-client-support:processTestResources NO-SOURCE
> Task :geode-old-client-support:testClasses
> Task :geode-old-client-support:checkMissedTests
> Task :geode-old-client-support:spotlessJava
> Task :geode-old-client-support:spotlessJavaCheck
> Task :geode-old-client-support:spotlessCheck
> Task :geode-old-client-support:test
> Task :geode-old-versions:javadocJar
> Task :geode-old-versions:sourcesJar
> Task :geode-old-versions:signArchives SKIPPED
> Task :geode-old-versions:assemble
> Task :geode-old-versions:compileTestJava
> Task :geode-old-versions:processTestResources NO-SOURCE
> Task :geode-old-versions:testClasses
> Task :geode-old-versions:checkMissedTests
> Task :geode-old-versions:spotlessJava
> Task :geode-old-versions:spotlessJavaCheck
> Task :geode-old-versions:spotlessCheck
> 

Re: trying to implement SSL configuration

[Ryan McMahon]

Hi Liron,


The first thing that jumps out to me when you say that GFSH could not
connect to the JMX manager is that you need to have `jmx` in addition to
`locator` in your `ssl-enabled-components` Geode system property.  For
example, you'd need ssl-enabled-components=locator,jmx at a minimum for
GFSH to connect.  it's a bit different if you pass --use-http to your
`connect` command, but it doesn't appear you are doing that.


Ryan

On Wed, Jun 20, 2018 at 8:46 AM, Liron Ben Ari 
wrote:

> Hi ,
> Well , I managed!! All my processes are talking with SSL configuration
> (hip hip Horay ☺)
> I figure out – that I need client authentication and server authentication
> in the server certificate EKU , and that I need a single  depth hierarchy ,
> I am not sure it will be the case when I wil need to implement it in the
> customer site…
>
> Does anyone have id why it was used like this?
>
>
> Last question…
> I am trying to configure the gfsh to connect to my locator.
> I’ve added to the connect command the needed properties…
>
>
> ${GEMFIRE_HOME}/bin/gfsh -e "connect --locator=192.168.2.100[1028]
> --use-ssl  --security-properties-file=$GF_SERVER_DIR/properties/
> gemfire.sec.properties
>
> I can see that he is able to connect to the locator – but I see that it is
> trying to connect to the manager without success.
> Does anyone know if I need to add another certificate or key for the
> manager?
>
>
> 1) Executing - connect --locator=192.168.2.100[1028] --use-ssl
> --security-properties-file=/users/xpiwrk1/GemFire/Server/
> properties/gemfire.sec.properties
>
> Connecting to Locator at [host=192.168.2.100, port=1028] ..
> Connecting to Manager at [host=eaasrt, port=1029] ..
> Could not connect to : [host=eaasrt, port=1029]. Failed to retrieve
> RMIServer stub: javax.naming.CommunicationException [Root exception is
> java.rmi.ConnectIOException: error during JRMP connection establishment;
> nested exception is:
> javax.net.ssl.SSLHandshakeException: Received fatal alert:
> handshake_failure]
>
>
>
> Thank you so much!!!
> From: Ernest Burghardt [mailto:eburgha...@pivotal.io]
> Sent: Tuesday, June 12, 2018 7:27 PM
> To: u...@geode.apache.org
> Cc: Udo Kohlmeyer ; dev@geode.apache.org; Gregory
> Vortman ; Vladi Polonsky
> ; Alon Bar-Lev 
> Subject: Re: trying to implement SSL configuration
>
> Hello,
>
> For "native" C++ interaction have a look at geode-native/cppcache/
> integration-test/testThinClientSSL
> This should provide an example of connecting with SSL enabled...
>
> EB
>
> On Tue, Jun 12, 2018 at 2:48 AM, Liron Ben Ari  mailto:liron.ben...@amdocs.com>> wrote:
>
> We check  - the PKCS12 works  - (as  we saw it in the s_client)
> It looks like the server did not found  a valid certificate...
>
> Maybe you have a working example? When the client is native c++?
>
> Thanks!!
>
> -Original Message-
> From: Liron Ben Ari
> Sent: Tuesday, June 12, 2018 11:25 AM
> To: Udo Kohlmeyer mailto:ukohlme...@pivotal.io>>;
> dev@geode.apache.org; u...@geode.apache.org
> 
> Cc: Gregory Vortman  gregory.vort...@amdocs.com>>; Vladi Polonsky  mailto:vladi.polon...@amdocs.com>>; Alon Bar-Lev  mailto:alon.bar...@amdocs.com>>
> Subject: RE: trying to implement SSL configuration
>
> Hi ,
> Thanks you for the quick respond.
> So according to the link you send, the keystore type is jks as well.
> I will try  and update...
> But according the client configuration (I found this document for it:
> http://pubs.vmware.com/vfabric53/topic/com.vmware.
> ICbase/PDF/vfabric-gemfire-nc-ug-7.0.1.pdf)
>
> The  keystore for the native client should be in PEM format.
>
>
>
> -Original Message-
> From: Udo Kohlmeyer [mailto:ukohlme...@pivotal.io ukohlme...@pivotal.io>]
> Sent: Tuesday, June 12, 2018 1:49 AM
> To: dev@geode.apache.org; Liron Ben Ari <
> liron.ben...@amdocs.com>;
> u...@geode.apache.org
> Cc: Gregory Vortman  gregory.vort...@amdocs.com>>; Vladi Polonsky  mailto:vladi.polon...@amdocs.com>>; Alon Bar-Lev  mailto:alon.bar...@amdocs.com>>
> Subject: Re: trying to implement SSL configuration
>
> Hi there,
>
> Have you tried the following?
>
> https://docs.oracle.com/cd/E19798-01/821-1841/gjrgy/index.html
>
> I have not tried to use a PKCS12 keystore type. Was there a particular
> reason why you are using it? Could you try with a JKS?
>
> --Udo
>
> On 6/11/18 03:31, Liron Ben Ari wrote:
> > Hello team.
> > I am trying to move my Client server to work with SSL as part of
> Security POC we are running .
> > I was moving on GEODE documents  (there are a lot! :)) and there was a
> lot of different options...
> >
> >
> >
> > This is the configuration  I used:
> >
> > I've generated Keystore & certificate using a private tool (that uses
> > the openssl + Keytools)
> >
> > For client:
> >   A file containing PEM encoded X.509 certificate and PEM encoded
> > PKCS#8 encrypted 

Re: trying to implement SSL configuration

[Jacob Barrett]

C++ client does not support certificate chaining. See GEODE-3415. Should be an 
easy fix if you want to submit a PR.

> On Jun 20, 2018, at 8:46 AM, Liron Ben Ari  wrote:
> 
> Hi ,
> Well , I managed!! All my processes are talking with SSL configuration (hip 
> hip Horay ☺)
> I figure out – that I need client authentication and server authentication in 
> the server certificate EKU , and that I need a single  depth hierarchy ,
> I am not sure it will be the case when I wil need to implement it in the 
> customer site…
> 
> Does anyone have id why it was used like this?
> 
> 
> Last question…
> I am trying to configure the gfsh to connect to my locator.
> I’ve added to the connect command the needed properties…
> 
> 
> ${GEMFIRE_HOME}/bin/gfsh -e "connect --locator=192.168.2.100[1028] --use-ssl  
> --security-properties-file=$GF_SERVER_DIR/properties/gemfire.sec.properties
> 
> I can see that he is able to connect to the locator – but I see that it is 
> trying to connect to the manager without success.
> Does anyone know if I need to add another certificate or key for the manager?
> 
> 
> 1) Executing - connect --locator=192.168.2.100[1028] --use-ssl  
> --security-properties-file=/users/xpiwrk1/GemFire/Server/properties/gemfire.sec.properties
> 
> Connecting to Locator at [host=192.168.2.100, port=1028] ..
> Connecting to Manager at [host=eaasrt, port=1029] ..
> Could not connect to : [host=eaasrt, port=1029]. Failed to retrieve RMIServer 
> stub: javax.naming.CommunicationException [Root exception is 
> java.rmi.ConnectIOException: error during JRMP connection establishment; 
> nested exception is:
>javax.net.ssl.SSLHandshakeException: Received fatal alert: 
> handshake_failure]
> 
> 
> 
> Thank you so much!!!
> From: Ernest Burghardt [mailto:eburgha...@pivotal.io]
> Sent: Tuesday, June 12, 2018 7:27 PM
> To: u...@geode.apache.org
> Cc: Udo Kohlmeyer ; dev@geode.apache.org; Gregory 
> Vortman ; Vladi Polonsky 
> ; Alon Bar-Lev 
> Subject: Re: trying to implement SSL configuration
> 
> Hello,
> 
> For "native" C++ interaction have a look at 
> geode-native/cppcache/integration-test/testThinClientSSL
> This should provide an example of connecting with SSL enabled...
> 
> EB
> 
> On Tue, Jun 12, 2018 at 2:48 AM, Liron Ben Ari 
> mailto:liron.ben...@amdocs.com>> wrote:
> 
> We check  - the PKCS12 works  - (as  we saw it in the s_client)
> It looks like the server did not found  a valid certificate...
> 
> Maybe you have a working example? When the client is native c++?
> 
> Thanks!!
> 
> -Original Message-
> From: Liron Ben Ari
> Sent: Tuesday, June 12, 2018 11:25 AM
> To: Udo Kohlmeyer mailto:ukohlme...@pivotal.io>>; 
> dev@geode.apache.org; 
> u...@geode.apache.org
> Cc: Gregory Vortman 
> mailto:gregory.vort...@amdocs.com>>; Vladi 
> Polonsky mailto:vladi.polon...@amdocs.com>>; Alon 
> Bar-Lev mailto:alon.bar...@amdocs.com>>
> Subject: RE: trying to implement SSL configuration
> 
> Hi ,
> Thanks you for the quick respond.
> So according to the link you send, the keystore type is jks as well.
> I will try  and update...
> But according the client configuration (I found this document for it: 
> http://pubs.vmware.com/vfabric53/topic/com.vmware.ICbase/PDF/vfabric-gemfire-nc-ug-7.0.1.pdf)
> 
> The  keystore for the native client should be in PEM format.
> 
> 
> 
> -Original Message-
> From: Udo Kohlmeyer 
> [mailto:ukohlme...@pivotal.io]
> Sent: Tuesday, June 12, 2018 1:49 AM
> To: dev@geode.apache.org; Liron Ben Ari 
> mailto:liron.ben...@amdocs.com>>; 
> u...@geode.apache.org
> Cc: Gregory Vortman 
> mailto:gregory.vort...@amdocs.com>>; Vladi 
> Polonsky mailto:vladi.polon...@amdocs.com>>; Alon 
> Bar-Lev mailto:alon.bar...@amdocs.com>>
> Subject: Re: trying to implement SSL configuration
> 
> Hi there,
> 
> Have you tried the following?
> 
> https://docs.oracle.com/cd/E19798-01/821-1841/gjrgy/index.html
> 
> I have not tried to use a PKCS12 keystore type. Was there a particular reason 
> why you are using it? Could you try with a JKS?
> 
> --Udo
> 
>> On 6/11/18 03:31, Liron Ben Ari wrote:
>> Hello team.
>> I am trying to move my Client server to work with SSL as part of Security 
>> POC we are running .
>> I was moving on GEODE documents  (there are a lot! :)) and there was a lot 
>> of different options...
>> 
>> 
>> 
>> This is the configuration  I used:
>> 
>> I've generated Keystore & certificate using a private tool (that uses
>> the openssl + Keytools)
>> 
>> For client:
>>  A file containing PEM encoded X.509 certificate and PEM encoded
>> PKCS#8 encrypted private key For server:
>> PKCS#12  - this part works
>> as we could see openssl s_client to return the chain
>> 
>> 
>> 
>> On the gemfire.proerties file - I used:
>> 
>> ssl-enabled-components=all
>> ssl-protocols=any
>> ssl-ciphers=SSL_RSA_WITH_NULL_SHA   //I've tries 

RE: trying to implement SSL configuration

[Liron Ben Ari]

Hi ,
Well , I managed!! All my processes are talking with SSL configuration (hip hip 
Horay ☺)
I figure out – that I need client authentication and server authentication in 
the server certificate EKU , and that I need a single  depth hierarchy ,
I am not sure it will be the case when I wil need to implement it in the 
customer site…

Does anyone have id why it was used like this?


Last question…
I am trying to configure the gfsh to connect to my locator.
I’ve added to the connect command the needed properties…


${GEMFIRE_HOME}/bin/gfsh -e "connect --locator=192.168.2.100[1028] --use-ssl  
--security-properties-file=$GF_SERVER_DIR/properties/gemfire.sec.properties

I can see that he is able to connect to the locator – but I see that it is 
trying to connect to the manager without success.
Does anyone know if I need to add another certificate or key for the manager?


1) Executing - connect --locator=192.168.2.100[1028] --use-ssl  
--security-properties-file=/users/xpiwrk1/GemFire/Server/properties/gemfire.sec.properties

Connecting to Locator at [host=192.168.2.100, port=1028] ..
Connecting to Manager at [host=eaasrt, port=1029] ..
Could not connect to : [host=eaasrt, port=1029]. Failed to retrieve RMIServer 
stub: javax.naming.CommunicationException [Root exception is 
java.rmi.ConnectIOException: error during JRMP connection establishment; nested 
exception is:
javax.net.ssl.SSLHandshakeException: Received fatal alert: 
handshake_failure]



Thank you so much!!!
From: Ernest Burghardt [mailto:eburgha...@pivotal.io]
Sent: Tuesday, June 12, 2018 7:27 PM
To: u...@geode.apache.org
Cc: Udo Kohlmeyer ; dev@geode.apache.org; Gregory 
Vortman ; Vladi Polonsky 
; Alon Bar-Lev 
Subject: Re: trying to implement SSL configuration

Hello,

For "native" C++ interaction have a look at 
geode-native/cppcache/integration-test/testThinClientSSL
This should provide an example of connecting with SSL enabled...

EB

On Tue, Jun 12, 2018 at 2:48 AM, Liron Ben Ari 
mailto:liron.ben...@amdocs.com>> wrote:

We check  - the PKCS12 works  - (as  we saw it in the s_client)
It looks like the server did not found  a valid certificate...

Maybe you have a working example? When the client is native c++?

Thanks!!

-Original Message-
From: Liron Ben Ari
Sent: Tuesday, June 12, 2018 11:25 AM
To: Udo Kohlmeyer mailto:ukohlme...@pivotal.io>>; 
dev@geode.apache.org; 
u...@geode.apache.org
Cc: Gregory Vortman 
mailto:gregory.vort...@amdocs.com>>; Vladi Polonsky 
mailto:vladi.polon...@amdocs.com>>; Alon Bar-Lev 
mailto:alon.bar...@amdocs.com>>
Subject: RE: trying to implement SSL configuration

Hi ,
Thanks you for the quick respond.
So according to the link you send, the keystore type is jks as well.
I will try  and update...
But according the client configuration (I found this document for it: 
http://pubs.vmware.com/vfabric53/topic/com.vmware.ICbase/PDF/vfabric-gemfire-nc-ug-7.0.1.pdf)

The  keystore for the native client should be in PEM format.



-Original Message-
From: Udo Kohlmeyer [mailto:ukohlme...@pivotal.io]
Sent: Tuesday, June 12, 2018 1:49 AM
To: dev@geode.apache.org; Liron Ben Ari 
mailto:liron.ben...@amdocs.com>>; 
u...@geode.apache.org
Cc: Gregory Vortman 
mailto:gregory.vort...@amdocs.com>>; Vladi Polonsky 
mailto:vladi.polon...@amdocs.com>>; Alon Bar-Lev 
mailto:alon.bar...@amdocs.com>>
Subject: Re: trying to implement SSL configuration

Hi there,

Have you tried the following?

https://docs.oracle.com/cd/E19798-01/821-1841/gjrgy/index.html

I have not tried to use a PKCS12 keystore type. Was there a particular reason 
why you are using it? Could you try with a JKS?

--Udo

On 6/11/18 03:31, Liron Ben Ari wrote:
> Hello team.
> I am trying to move my Client server to work with SSL as part of Security POC 
> we are running .
> I was moving on GEODE documents  (there are a lot! :)) and there was a lot of 
> different options...
>
>
>
> This is the configuration  I used:
>
> I've generated Keystore & certificate using a private tool (that uses
> the openssl + Keytools)
>
> For client:
>   A file containing PEM encoded X.509 certificate and PEM encoded
> PKCS#8 encrypted private key For server:
> PKCS#12  - this part works
> as we could see openssl s_client to return the chain
>
>
>
> On the gemfire.proerties file - I used:
>
> ssl-enabled-components=all
> ssl-protocols=any
> ssl-ciphers=SSL_RSA_WITH_NULL_SHA   //I've tries both option (empty as 
> well)
> ssl-keystore-type=PKCS12
> ssl-keystore=/users/xpiwrk1/Amdocs-Test-CA/pki/private/server4.p12
> ssl-keystore-password=changeme
> ssl-truststore-type=JKS
> ssl-truststore=/users/xpiwrk1/Amdocs-Test-CA/AmdocsTestCA-Trust.jks
> ssl-truststore-password=changeit
>
>
>
> on the Client Side I used the PEM format:
> gfcpp1.properties:
> ssl-enabled=true
> ssl-keystore=/tmp/server4.pem
> 

Geode unit tests completed in 'develop/FlakyTest' with non-zero exit code

[apachegeodeci]

Pipeline results can be found at:

Concourse: 
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/FlakyTest/builds/97

Geode unit tests 'develop/DistributedTest' took too long to execute

[apachegeodeci]

Pipeline results can be found at:

Concourse: 
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/71