Re: [VOTE] Release Apache Mesos 1.6.2 (rc1)

2019-02-20 Thread Meng Zhu
+1 -- ran on centos 7.4 with only known flaky tests -Meng On Wed, Feb 20, 2019 at 4:57 PM Gastón Kleiman wrote: > +1 (binding) — ran the build through Mesosphere's internal CI and only two > known flaky tests failed. > > On Tue, Feb 19, 2019 at 11:56 AM Greg Mann wrote: > >> Hi all, >> >>

Re: [VOTE] Release Apache Mesos 1.6.2 (rc1)

2019-02-20 Thread Gastón Kleiman
+1 (binding) — ran the build through Mesosphere's internal CI and only two known flaky tests failed. On Tue, Feb 19, 2019 at 11:56 AM Greg Mann wrote: > Hi all, > > Please vote on releasing the following candidate as Apache Mesos 1.6.2. > > > 1.6.2 includes a number of bug fixes since 1.6.1;

Re: Failed to accept socket: Failed accept: connection error: error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request

2019-02-20 Thread Joseph Wu
The "SSL routines:SSL23_GET_CLIENT_HELLO:http request" is OpenSSL's cryptic way of saying the client is using HTTP to talk to an HTTPS server. Since you've disabled LIBPROCESS_SSL_SUPPORT_DOWNGRADE, the error should be expected. On Wed, Feb 20, 2019 at 2:06 PM Marc Roos wrote: > > > Why am I

Executors cannot register with SSL-required agent MESOS-3815

2019-02-20 Thread Marc Roos
What is the recommended work around for this? Except for the obvious and ssl downgrade. https://issues.apache.org/jira/browse/MESOS-3815

Failed to accept socket: Failed accept: connection error: error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request

2019-02-20 Thread Marc Roos
Why am I getting these when I connect with at browser to port 5050. How to resolve this, looks like a bug or so. 192.168.10.151 has the same cert as m1.local and the cert has even common name m01.local. But the javascript is reporting "An error occurred: SEC_ERROR_UNKNOWN_ISSUER" W0220

Re: [VOTE] Release Apache Mesos 1.6.2 (rc1)

2019-02-20 Thread Vinod Kone
+1 (binding) Thanks for the update Greg. On Wed, Feb 20, 2019 at 11:41 AM Greg Mann wrote: > It appears to be a flaky test; that particular failure hasn't come up in > the CI builds that I ran, or in my own manual testing. Just now, I was able > to get that test to fail after many repetitions,

Re: [VOTE] Release Apache Mesos 1.6.2 (rc1)

2019-02-20 Thread Greg Mann
It appears to be a flaky test; that particular failure hasn't come up in the CI builds that I ran, or in my own manual testing. Just now, I was able to get that test to fail after many repetitions, but with a different error. I filed ticket MESOS-9589

Re: [VOTE] Release Apache Mesos 1.7.2 (rc1)

2019-02-20 Thread Vinod Kone
+1 Ran this on ASF CI. The red builds are a flaky infra issue and a known flaky test . *Revision*: 58cc918e9acc2865bb07047d3d2dff156d1708b2 - refs/tags/1.7.2-rc1 Configuration Matrix gcc clang centos:7 --verbose --disable-libtool-wrappers