The http1 and http2 code in the Http2SolrClient ultimately create different errors when there are TLS issues. So the fix was merely to accept both types of errors, when checking the output of failed commands.
These should be fixed on main, branch_9x and branch_9_4. So let's give it a day and see what other lovely errors are left for us to deal with in Jenkins! - Houston On Mon, Oct 30, 2023 at 11:57 AM Houston Putman <hous...@apache.org> wrote: > Ok, I've determined that the mTLS errors are due to using http1 vs http2 > in the client. > I'm not sure why http1 is used by default in different environments (Its > enabled by the `-Dsolr.http1=true` System Property), > but now at least the cause is known. I'll try to fix the ssl integration > tests for the http1 client today. > > - Houston > > On Mon, Oct 30, 2023 at 10:58 AM Houston Putman <hous...@apache.org> > wrote: > >> If you scroll down on the output of >> https://builds.apache.org/job/Solr/job/Solr-Check-main/8273, you can see >> it in the integration tests. >> Search for "not ok 75 start solr with mTLS needed" >> >> For the builds using crave.io (Solr-Check-9.x), the same failures will >> happen but every time. The builds using the jenkins boxes >> (Solr-Check-main), will only fail these integration tests if they use the* >> lucene-solr-1* machine. >> >> - Houston >> >> On Sat, Oct 28, 2023 at 12:46 PM Mikhail Khludnev <m...@apache.org> >> wrote: >> >>> Hello Houston. >>> Thanks for your efforts. How can I check that "MTLs issue"? I looked >>> through recent failures, but can't find anything. >>> >>
