Re: [Operator] [VOTE] Release the Solr Operator v0.3.0 RC2

2021-04-21 Thread Timothy Potter
+1 (binding) Ran the smoke tester and deployed a 3-node to GKE with TLS + basic auth + anti-affinity + auto-scaling policy + prom / grafana metrics + zone aware query routing ~ the works! Thank you for the amazing work on this release Houston. On Wed, Apr 21, 2021 at 3:55 PM Houston Putman wrot

[Operator] [VOTE] Release the Solr Operator v0.3.0 RC2

2021-04-21 Thread Houston Putman
Please vote for release candidate 2 for the Solr Operator v0.3.0 The artifacts can be downloaded from: https://dist.apache.org/repos/dist/dev/solr/solr-operator/solr-operator-v0.3.0-RC2-rev4ec41cb3ebf879b352dc08ae5f789c6ff86b7a04 You can run the full smoke tester, with instructions below. However

Re: precommit is broken

2021-04-21 Thread David Smiley
Oh jeesh I'm sorry; I'll fix now. ~ David Smiley Apache Lucene/Solr Search Developer http://www.linkedin.com/in/davidwsmiley On Wed, Apr 21, 2021 at 3:49 PM Timothy Potter wrote: > Looks like your latest commit David --> > > https://github.com/apache/solr/commit/7877c914b9035422e380251be42948b

precommit is broken

2021-04-21 Thread Timothy Potter
Looks like your latest commit David --> https://github.com/apache/solr/commit/7877c914b9035422e380251be42948b924fe72fa > Task :solr:core:ecjLintTest 164-- 1651. ERROR in /home/runner/work/solr/solr/solr/core/src/test/org/apache/solr/handler/admin/LukeRequestHandlerTest.java (at line 22) 1

[Operator] [FAILED] [VOTE] Release the Solr Operator v0.3.0 RC1

2021-04-21 Thread Houston Putman
It's been >72h since the vote was initiated and the result is: +1 1 (1 binding) 0 2 -1 1 Reason for failing is too few binding votes. This vote has FAILED

Re: [Operator] [VOTE] Release the Solr Operator v0.3.0 RC1

2021-04-21 Thread Houston Putman
It's been >72h since the vote was initiated and the result is: +1 1 (1 binding) 0 2 -1 1 Reason for failing is too few binding votes. This vote has FAILED Thanks everyone for all of their help debugging this first RC. You can follow along with the changes to address these issues at: https