You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by Christopher <ct...@apache.org> on 2018/03/19 19:44:19 UTC
[VOTE] Accumulo 1.7.4-rc1
Accumulo Developers,
Please consider the following candidate for Accumulo 1.7.4.
Git Commit:
b2a59189108d736729432e81b3d5717000c6b891
Branch:
1.7.4-rc1
If this vote passes, a gpg-signed tag will be created using:
git tag -f -m 'Apache Accumulo 1.7.4' -s rel/1.7.4 \
b2a59189108d736729432e81b3d5717000c6b891
Staging repo:
https://repository.apache.org/content/repositories/orgapacheaccumulo-1068
Source (official release artifact):
https://repository.apache.org/content/repositories/orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.4/accumulo-1.7.4-src.tar.gz
Binary:
https://repository.apache.org/content/repositories/orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.4/accumulo-1.7.4-bin.tar.gz
(Append ".sha1", ".md5", or ".asc" to download the signature/hash for a
given artifact.)
All artifacts were built and staged with:
mvn release:prepare && mvn release:perform
Signing keys are available at https://www.apache.org/dist/accumulo/KEYS
(Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
Release notes (in progress) can be found at:
https://accumulo.apache.org/release/accumulo-1.7.4/
Please vote one of:
[ ] +1 - I have verified and accept...
[ ] +0 - I have reservations, but not strong enough to vote against...
[ ] -1 - Because..., I do not accept...
... these artifacts as the 1.7.4 release of Apache Accumulo.
This vote will remain open until at least Thu Mar 22 20:00:00 UTC 2018
(Thu Mar 22 16:00:00 EDT 2018 / Thu Mar 22 13:00:00 PDT 2018).
Voting continues until the release manager sends an email closing the vote.
Thanks!
P.S. Hint: download the whole staging repo with
wget -erobots=off -r -l inf -np -nH \
https://repository.apache.org/content/repositories/orgapacheaccumulo-1068/
# note the trailing slash is needed
Re: [VOTE] Accumulo 1.7.4-rc1
Posted by Josh Elser <el...@apache.org>.
Yup, that's the only thing that would have come to my mind (hadoop bugs
that have been long-fixed).
On 3/22/18 10:07 PM, Christopher wrote:
> Yeah, I vaguely remember that now. It definitely seems to be the problem
> here. I believe it is one of the reasons we moved to 2.6.4 in 1.8+
>
> I had forgotten about that. The 1.7 branch was still building with Hadoop
> 2.2.0 and I now do my testing with jdk8 only, so that's why it kept being a
> problem for me.
>
> Thanks for the info. I spent way too much time this week looking into this
> when all I needed to do was test with a newer version of Hadoop (or an
> older version of jdk), but at least I now know what the problem was.
>
> On Thu, Mar 22, 2018, 21:15 Billie Rinaldi <bi...@gmail.com> wrote:
>
>> On Thu, Mar 22, 2018 at 2:31 PM, Christopher <ct...@apache.org> wrote:
>>
>>> Josh, I know you said you didn't have much time, but just in case you
>> get a
>>> moment: do you know why `UserGroupInformation.isLoginKeytabBased()` might
>>> be false on the server side? This seems to be the root cause of the
>>> problems.
>>>
>>
>> I recall running into HADOOP-10786 a while ago ("in java 8 isKeyTab is
>> always false given the current UGI implementation"). Not sure if that would
>> be relevant here.
>>
>>
>>>
>>> https://github.com/apache/accumulo/blob/b0016c3ca36e15ee4bdde727ea5b6a
>>> 18597de0ff/core/src/main/java/org/apache/accumulo/core/rpc/
>>> ThriftUtil.java#L383
>>>
>>>
>>> On Thu, Mar 22, 2018 at 4:00 PM Josh Elser <el...@apache.org> wrote:
>>>
>>>> I don't have the time to look at these right now. There isn't much
>>>> special about how Accumulo uses Kerberos either. It's straightforward
>>>> use via SASL with Thrift. I haven't looked at it since it was passing
>>>> when I wrote it originally.
>>>>
>>>> On 3/20/18 2:32 PM, Christopher wrote:
>>>>> I'm currently looking at the KerberosRenewalIT failures that seem to
>> be
>>>>> persisting across branches. From the logs, it looks like the accumulo
>>>>> services are trying to do ticket-cache based login renewals, instead
>> of
>>>>> keytab-based renewals. This has been a problematic test for me
>> before,
>>>>> and as such, I've gotten into the habit of ignoring it, but since
>> I've
>>>>> not been able to get it to work on reruns, and it fails nearly 100%
>> of
>>>>> the time (if not 100%) for me now, I decided to take a closer look.
>> If
>>>>> it is doing ticket-cache based renewals, that could indicate a bug in
>>>>> the Kerberos authentication, and that would probably warrant a -1
>> from
>>>>> me... but I will continue to investigate first.
>>>>>
>>>>> Josh, you know more about the Kerberos stuff than anyone here, so if
>>> you
>>>>> have time/interest, I wouldn't mind getting your feedback on why this
>>>>> test might be failing for me.
>>>>>
>>>>> On Mon, Mar 19, 2018 at 3:44 PM Christopher <ctubbsii@apache.org
>>>>> <ma...@apache.org>> wrote:
>>>>>
>>>>> Accumulo Developers,
>>>>>
>>>>> Please consider the following candidate for Accumulo 1.7.4.
>>>>>
>>>>> Git Commit:
>>>>> b2a59189108d736729432e81b3d5717000c6b891
>>>>> Branch:
>>>>> 1.7.4-rc1
>>>>>
>>>>> If this vote passes, a gpg-signed tag will be created using:
>>>>> git tag -f -m 'Apache Accumulo 1.7.4' -s rel/1.7.4 \
>>>>> b2a59189108d736729432e81b3d5717000c6b891
>>>>>
>>>>> Staging repo:
>>>>>
>>>> https://repository.apache.org/content/repositories/
>>> orgapacheaccumulo-1068
>>>>> Source (official release artifact):
>>>>>
>>>> https://repository.apache.org/content/repositories/
>>> orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
>>> 4/accumulo-1.7.4-src.tar.gz
>>>>> Binary:
>>>>>
>>>> https://repository.apache.org/content/repositories/
>>> orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
>>> 4/accumulo-1.7.4-bin.tar.gz
>>>>> (Append ".sha1", ".md5", or ".asc" to download the signature/hash
>>>>> for a given artifact.)
>>>>>
>>>>> All artifacts were built and staged with:
>>>>> mvn release:prepare && mvn release:perform
>>>>>
>>>>> Signing keys are available at
>>>> https://www.apache.org/dist/accumulo/KEYS
>>>>> (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
>>>>>
>>>>> Release notes (in progress) can be found at:
>>>>> https://accumulo.apache.org/release/accumulo-1.7.4/
>>>>>
>>>>> Please vote one of:
>>>>> [ ] +1 - I have verified and accept...
>>>>> [ ] +0 - I have reservations, but not strong enough to vote
>>>> against...
>>>>> [ ] -1 - Because..., I do not accept...
>>>>> ... these artifacts as the 1.7.4 release of Apache Accumulo.
>>>>>
>>>>> This vote will remain open until at least Thu Mar 22 20:00:00 UTC
>>>> 2018
>>>>> (Thu Mar 22 16:00:00 EDT 2018 / Thu Mar 22 13:00:00 PDT 2018).
>>>>> Voting continues until the release manager sends an email closing
>>>>> the vote.
>>>>>
>>>>> Thanks!
>>>>>
>>>>> P.S. Hint: download the whole staging repo with
>>>>> wget -erobots=off -r -l inf -np -nH \
>>>>>
>>>> https://repository.apache.org/content/repositories/
>>> orgapacheaccumulo-1068/
>>>>> # note the trailing slash is needed
>>>>>
>>>>
>>>
>>
>
Re: [VOTE] Accumulo 1.7.4-rc1
Posted by Christopher <ct...@apache.org>.
Yeah, I vaguely remember that now. It definitely seems to be the problem
here. I believe it is one of the reasons we moved to 2.6.4 in 1.8+
I had forgotten about that. The 1.7 branch was still building with Hadoop
2.2.0 and I now do my testing with jdk8 only, so that's why it kept being a
problem for me.
Thanks for the info. I spent way too much time this week looking into this
when all I needed to do was test with a newer version of Hadoop (or an
older version of jdk), but at least I now know what the problem was.
On Thu, Mar 22, 2018, 21:15 Billie Rinaldi <bi...@gmail.com> wrote:
> On Thu, Mar 22, 2018 at 2:31 PM, Christopher <ct...@apache.org> wrote:
>
> > Josh, I know you said you didn't have much time, but just in case you
> get a
> > moment: do you know why `UserGroupInformation.isLoginKeytabBased()` might
> > be false on the server side? This seems to be the root cause of the
> > problems.
> >
>
> I recall running into HADOOP-10786 a while ago ("in java 8 isKeyTab is
> always false given the current UGI implementation"). Not sure if that would
> be relevant here.
>
>
> >
> > https://github.com/apache/accumulo/blob/b0016c3ca36e15ee4bdde727ea5b6a
> > 18597de0ff/core/src/main/java/org/apache/accumulo/core/rpc/
> > ThriftUtil.java#L383
> >
> >
> > On Thu, Mar 22, 2018 at 4:00 PM Josh Elser <el...@apache.org> wrote:
> >
> > > I don't have the time to look at these right now. There isn't much
> > > special about how Accumulo uses Kerberos either. It's straightforward
> > > use via SASL with Thrift. I haven't looked at it since it was passing
> > > when I wrote it originally.
> > >
> > > On 3/20/18 2:32 PM, Christopher wrote:
> > > > I'm currently looking at the KerberosRenewalIT failures that seem to
> be
> > > > persisting across branches. From the logs, it looks like the accumulo
> > > > services are trying to do ticket-cache based login renewals, instead
> of
> > > > keytab-based renewals. This has been a problematic test for me
> before,
> > > > and as such, I've gotten into the habit of ignoring it, but since
> I've
> > > > not been able to get it to work on reruns, and it fails nearly 100%
> of
> > > > the time (if not 100%) for me now, I decided to take a closer look.
> If
> > > > it is doing ticket-cache based renewals, that could indicate a bug in
> > > > the Kerberos authentication, and that would probably warrant a -1
> from
> > > > me... but I will continue to investigate first.
> > > >
> > > > Josh, you know more about the Kerberos stuff than anyone here, so if
> > you
> > > > have time/interest, I wouldn't mind getting your feedback on why this
> > > > test might be failing for me.
> > > >
> > > > On Mon, Mar 19, 2018 at 3:44 PM Christopher <ctubbsii@apache.org
> > > > <ma...@apache.org>> wrote:
> > > >
> > > > Accumulo Developers,
> > > >
> > > > Please consider the following candidate for Accumulo 1.7.4.
> > > >
> > > > Git Commit:
> > > > b2a59189108d736729432e81b3d5717000c6b891
> > > > Branch:
> > > > 1.7.4-rc1
> > > >
> > > > If this vote passes, a gpg-signed tag will be created using:
> > > > git tag -f -m 'Apache Accumulo 1.7.4' -s rel/1.7.4 \
> > > > b2a59189108d736729432e81b3d5717000c6b891
> > > >
> > > > Staging repo:
> > > >
> > > https://repository.apache.org/content/repositories/
> > orgapacheaccumulo-1068
> > > > Source (official release artifact):
> > > >
> > > https://repository.apache.org/content/repositories/
> > orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
> > 4/accumulo-1.7.4-src.tar.gz
> > > > Binary:
> > > >
> > > https://repository.apache.org/content/repositories/
> > orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
> > 4/accumulo-1.7.4-bin.tar.gz
> > > > (Append ".sha1", ".md5", or ".asc" to download the signature/hash
> > > > for a given artifact.)
> > > >
> > > > All artifacts were built and staged with:
> > > > mvn release:prepare && mvn release:perform
> > > >
> > > > Signing keys are available at
> > > https://www.apache.org/dist/accumulo/KEYS
> > > > (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
> > > >
> > > > Release notes (in progress) can be found at:
> > > > https://accumulo.apache.org/release/accumulo-1.7.4/
> > > >
> > > > Please vote one of:
> > > > [ ] +1 - I have verified and accept...
> > > > [ ] +0 - I have reservations, but not strong enough to vote
> > > against...
> > > > [ ] -1 - Because..., I do not accept...
> > > > ... these artifacts as the 1.7.4 release of Apache Accumulo.
> > > >
> > > > This vote will remain open until at least Thu Mar 22 20:00:00 UTC
> > > 2018
> > > > (Thu Mar 22 16:00:00 EDT 2018 / Thu Mar 22 13:00:00 PDT 2018).
> > > > Voting continues until the release manager sends an email closing
> > > > the vote.
> > > >
> > > > Thanks!
> > > >
> > > > P.S. Hint: download the whole staging repo with
> > > > wget -erobots=off -r -l inf -np -nH \
> > > >
> > > https://repository.apache.org/content/repositories/
> > orgapacheaccumulo-1068/
> > > > # note the trailing slash is needed
> > > >
> > >
> >
>
Re: [VOTE] Accumulo 1.7.4-rc1
Posted by Billie Rinaldi <bi...@gmail.com>.
On Thu, Mar 22, 2018 at 2:31 PM, Christopher <ct...@apache.org> wrote:
> Josh, I know you said you didn't have much time, but just in case you get a
> moment: do you know why `UserGroupInformation.isLoginKeytabBased()` might
> be false on the server side? This seems to be the root cause of the
> problems.
>
I recall running into HADOOP-10786 a while ago ("in java 8 isKeyTab is
always false given the current UGI implementation"). Not sure if that would
be relevant here.
>
> https://github.com/apache/accumulo/blob/b0016c3ca36e15ee4bdde727ea5b6a
> 18597de0ff/core/src/main/java/org/apache/accumulo/core/rpc/
> ThriftUtil.java#L383
>
>
> On Thu, Mar 22, 2018 at 4:00 PM Josh Elser <el...@apache.org> wrote:
>
> > I don't have the time to look at these right now. There isn't much
> > special about how Accumulo uses Kerberos either. It's straightforward
> > use via SASL with Thrift. I haven't looked at it since it was passing
> > when I wrote it originally.
> >
> > On 3/20/18 2:32 PM, Christopher wrote:
> > > I'm currently looking at the KerberosRenewalIT failures that seem to be
> > > persisting across branches. From the logs, it looks like the accumulo
> > > services are trying to do ticket-cache based login renewals, instead of
> > > keytab-based renewals. This has been a problematic test for me before,
> > > and as such, I've gotten into the habit of ignoring it, but since I've
> > > not been able to get it to work on reruns, and it fails nearly 100% of
> > > the time (if not 100%) for me now, I decided to take a closer look. If
> > > it is doing ticket-cache based renewals, that could indicate a bug in
> > > the Kerberos authentication, and that would probably warrant a -1 from
> > > me... but I will continue to investigate first.
> > >
> > > Josh, you know more about the Kerberos stuff than anyone here, so if
> you
> > > have time/interest, I wouldn't mind getting your feedback on why this
> > > test might be failing for me.
> > >
> > > On Mon, Mar 19, 2018 at 3:44 PM Christopher <ctubbsii@apache.org
> > > <ma...@apache.org>> wrote:
> > >
> > > Accumulo Developers,
> > >
> > > Please consider the following candidate for Accumulo 1.7.4.
> > >
> > > Git Commit:
> > > b2a59189108d736729432e81b3d5717000c6b891
> > > Branch:
> > > 1.7.4-rc1
> > >
> > > If this vote passes, a gpg-signed tag will be created using:
> > > git tag -f -m 'Apache Accumulo 1.7.4' -s rel/1.7.4 \
> > > b2a59189108d736729432e81b3d5717000c6b891
> > >
> > > Staging repo:
> > >
> > https://repository.apache.org/content/repositories/
> orgapacheaccumulo-1068
> > > Source (official release artifact):
> > >
> > https://repository.apache.org/content/repositories/
> orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
> 4/accumulo-1.7.4-src.tar.gz
> > > Binary:
> > >
> > https://repository.apache.org/content/repositories/
> orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
> 4/accumulo-1.7.4-bin.tar.gz
> > > (Append ".sha1", ".md5", or ".asc" to download the signature/hash
> > > for a given artifact.)
> > >
> > > All artifacts were built and staged with:
> > > mvn release:prepare && mvn release:perform
> > >
> > > Signing keys are available at
> > https://www.apache.org/dist/accumulo/KEYS
> > > (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
> > >
> > > Release notes (in progress) can be found at:
> > > https://accumulo.apache.org/release/accumulo-1.7.4/
> > >
> > > Please vote one of:
> > > [ ] +1 - I have verified and accept...
> > > [ ] +0 - I have reservations, but not strong enough to vote
> > against...
> > > [ ] -1 - Because..., I do not accept...
> > > ... these artifacts as the 1.7.4 release of Apache Accumulo.
> > >
> > > This vote will remain open until at least Thu Mar 22 20:00:00 UTC
> > 2018
> > > (Thu Mar 22 16:00:00 EDT 2018 / Thu Mar 22 13:00:00 PDT 2018).
> > > Voting continues until the release manager sends an email closing
> > > the vote.
> > >
> > > Thanks!
> > >
> > > P.S. Hint: download the whole staging repo with
> > > wget -erobots=off -r -l inf -np -nH \
> > >
> > https://repository.apache.org/content/repositories/
> orgapacheaccumulo-1068/
> > > # note the trailing slash is needed
> > >
> >
>
Re: [VOTE] Accumulo 1.7.4-rc1
Posted by Christopher <ct...@apache.org>.
Josh, I know you said you didn't have much time, but just in case you get a
moment: do you know why `UserGroupInformation.isLoginKeytabBased()` might
be false on the server side? This seems to be the root cause of the
problems.
https://github.com/apache/accumulo/blob/b0016c3ca36e15ee4bdde727ea5b6a18597de0ff/core/src/main/java/org/apache/accumulo/core/rpc/ThriftUtil.java#L383
On Thu, Mar 22, 2018 at 4:00 PM Josh Elser <el...@apache.org> wrote:
> I don't have the time to look at these right now. There isn't much
> special about how Accumulo uses Kerberos either. It's straightforward
> use via SASL with Thrift. I haven't looked at it since it was passing
> when I wrote it originally.
>
> On 3/20/18 2:32 PM, Christopher wrote:
> > I'm currently looking at the KerberosRenewalIT failures that seem to be
> > persisting across branches. From the logs, it looks like the accumulo
> > services are trying to do ticket-cache based login renewals, instead of
> > keytab-based renewals. This has been a problematic test for me before,
> > and as such, I've gotten into the habit of ignoring it, but since I've
> > not been able to get it to work on reruns, and it fails nearly 100% of
> > the time (if not 100%) for me now, I decided to take a closer look. If
> > it is doing ticket-cache based renewals, that could indicate a bug in
> > the Kerberos authentication, and that would probably warrant a -1 from
> > me... but I will continue to investigate first.
> >
> > Josh, you know more about the Kerberos stuff than anyone here, so if you
> > have time/interest, I wouldn't mind getting your feedback on why this
> > test might be failing for me.
> >
> > On Mon, Mar 19, 2018 at 3:44 PM Christopher <ctubbsii@apache.org
> > <ma...@apache.org>> wrote:
> >
> > Accumulo Developers,
> >
> > Please consider the following candidate for Accumulo 1.7.4.
> >
> > Git Commit:
> > b2a59189108d736729432e81b3d5717000c6b891
> > Branch:
> > 1.7.4-rc1
> >
> > If this vote passes, a gpg-signed tag will be created using:
> > git tag -f -m 'Apache Accumulo 1.7.4' -s rel/1.7.4 \
> > b2a59189108d736729432e81b3d5717000c6b891
> >
> > Staging repo:
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1068
> > Source (official release artifact):
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.4/accumulo-1.7.4-src.tar.gz
> > Binary:
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.4/accumulo-1.7.4-bin.tar.gz
> > (Append ".sha1", ".md5", or ".asc" to download the signature/hash
> > for a given artifact.)
> >
> > All artifacts were built and staged with:
> > mvn release:prepare && mvn release:perform
> >
> > Signing keys are available at
> https://www.apache.org/dist/accumulo/KEYS
> > (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
> >
> > Release notes (in progress) can be found at:
> > https://accumulo.apache.org/release/accumulo-1.7.4/
> >
> > Please vote one of:
> > [ ] +1 - I have verified and accept...
> > [ ] +0 - I have reservations, but not strong enough to vote
> against...
> > [ ] -1 - Because..., I do not accept...
> > ... these artifacts as the 1.7.4 release of Apache Accumulo.
> >
> > This vote will remain open until at least Thu Mar 22 20:00:00 UTC
> 2018
> > (Thu Mar 22 16:00:00 EDT 2018 / Thu Mar 22 13:00:00 PDT 2018).
> > Voting continues until the release manager sends an email closing
> > the vote.
> >
> > Thanks!
> >
> > P.S. Hint: download the whole staging repo with
> > wget -erobots=off -r -l inf -np -nH \
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1068/
> > # note the trailing slash is needed
> >
>
Re: [VOTE] Accumulo 1.7.4-rc1
Posted by Christopher <ct...@apache.org>.
Understood. I'll ignore the failures for now, and vote based on other
factors.
On Thu, Mar 22, 2018 at 4:00 PM Josh Elser <el...@apache.org> wrote:
> I don't have the time to look at these right now. There isn't much
> special about how Accumulo uses Kerberos either. It's straightforward
> use via SASL with Thrift. I haven't looked at it since it was passing
> when I wrote it originally.
>
> On 3/20/18 2:32 PM, Christopher wrote:
> > I'm currently looking at the KerberosRenewalIT failures that seem to be
> > persisting across branches. From the logs, it looks like the accumulo
> > services are trying to do ticket-cache based login renewals, instead of
> > keytab-based renewals. This has been a problematic test for me before,
> > and as such, I've gotten into the habit of ignoring it, but since I've
> > not been able to get it to work on reruns, and it fails nearly 100% of
> > the time (if not 100%) for me now, I decided to take a closer look. If
> > it is doing ticket-cache based renewals, that could indicate a bug in
> > the Kerberos authentication, and that would probably warrant a -1 from
> > me... but I will continue to investigate first.
> >
> > Josh, you know more about the Kerberos stuff than anyone here, so if you
> > have time/interest, I wouldn't mind getting your feedback on why this
> > test might be failing for me.
> >
> > On Mon, Mar 19, 2018 at 3:44 PM Christopher <ctubbsii@apache.org
> > <ma...@apache.org>> wrote:
> >
> > Accumulo Developers,
> >
> > Please consider the following candidate for Accumulo 1.7.4.
> >
> > Git Commit:
> > b2a59189108d736729432e81b3d5717000c6b891
> > Branch:
> > 1.7.4-rc1
> >
> > If this vote passes, a gpg-signed tag will be created using:
> > git tag -f -m 'Apache Accumulo 1.7.4' -s rel/1.7.4 \
> > b2a59189108d736729432e81b3d5717000c6b891
> >
> > Staging repo:
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1068
> > Source (official release artifact):
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.4/accumulo-1.7.4-src.tar.gz
> > Binary:
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.4/accumulo-1.7.4-bin.tar.gz
> > (Append ".sha1", ".md5", or ".asc" to download the signature/hash
> > for a given artifact.)
> >
> > All artifacts were built and staged with:
> > mvn release:prepare && mvn release:perform
> >
> > Signing keys are available at
> https://www.apache.org/dist/accumulo/KEYS
> > (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
> >
> > Release notes (in progress) can be found at:
> > https://accumulo.apache.org/release/accumulo-1.7.4/
> >
> > Please vote one of:
> > [ ] +1 - I have verified and accept...
> > [ ] +0 - I have reservations, but not strong enough to vote
> against...
> > [ ] -1 - Because..., I do not accept...
> > ... these artifacts as the 1.7.4 release of Apache Accumulo.
> >
> > This vote will remain open until at least Thu Mar 22 20:00:00 UTC
> 2018
> > (Thu Mar 22 16:00:00 EDT 2018 / Thu Mar 22 13:00:00 PDT 2018).
> > Voting continues until the release manager sends an email closing
> > the vote.
> >
> > Thanks!
> >
> > P.S. Hint: download the whole staging repo with
> > wget -erobots=off -r -l inf -np -nH \
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1068/
> > # note the trailing slash is needed
> >
>
Re: [VOTE] Accumulo 1.7.4-rc1
Posted by Josh Elser <el...@apache.org>.
I don't have the time to look at these right now. There isn't much
special about how Accumulo uses Kerberos either. It's straightforward
use via SASL with Thrift. I haven't looked at it since it was passing
when I wrote it originally.
On 3/20/18 2:32 PM, Christopher wrote:
> I'm currently looking at the KerberosRenewalIT failures that seem to be
> persisting across branches. From the logs, it looks like the accumulo
> services are trying to do ticket-cache based login renewals, instead of
> keytab-based renewals. This has been a problematic test for me before,
> and as such, I've gotten into the habit of ignoring it, but since I've
> not been able to get it to work on reruns, and it fails nearly 100% of
> the time (if not 100%) for me now, I decided to take a closer look. If
> it is doing ticket-cache based renewals, that could indicate a bug in
> the Kerberos authentication, and that would probably warrant a -1 from
> me... but I will continue to investigate first.
>
> Josh, you know more about the Kerberos stuff than anyone here, so if you
> have time/interest, I wouldn't mind getting your feedback on why this
> test might be failing for me.
>
> On Mon, Mar 19, 2018 at 3:44 PM Christopher <ctubbsii@apache.org
> <ma...@apache.org>> wrote:
>
> Accumulo Developers,
>
> Please consider the following candidate for Accumulo 1.7.4.
>
> Git Commit:
> b2a59189108d736729432e81b3d5717000c6b891
> Branch:
> 1.7.4-rc1
>
> If this vote passes, a gpg-signed tag will be created using:
> git tag -f -m 'Apache Accumulo 1.7.4' -s rel/1.7.4 \
> b2a59189108d736729432e81b3d5717000c6b891
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1068
> Source (official release artifact):
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.4/accumulo-1.7.4-src.tar.gz
> Binary:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.4/accumulo-1.7.4-bin.tar.gz
> (Append ".sha1", ".md5", or ".asc" to download the signature/hash
> for a given artifact.)
>
> All artifacts were built and staged with:
> mvn release:prepare && mvn release:perform
>
> Signing keys are available at https://www.apache.org/dist/accumulo/KEYS
> (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
>
> Release notes (in progress) can be found at:
> https://accumulo.apache.org/release/accumulo-1.7.4/
>
> Please vote one of:
> [ ] +1 - I have verified and accept...
> [ ] +0 - I have reservations, but not strong enough to vote against...
> [ ] -1 - Because..., I do not accept...
> ... these artifacts as the 1.7.4 release of Apache Accumulo.
>
> This vote will remain open until at least Thu Mar 22 20:00:00 UTC 2018
> (Thu Mar 22 16:00:00 EDT 2018 / Thu Mar 22 13:00:00 PDT 2018).
> Voting continues until the release manager sends an email closing
> the vote.
>
> Thanks!
>
> P.S. Hint: download the whole staging repo with
> wget -erobots=off -r -l inf -np -nH \
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1068/
> # note the trailing slash is needed
>
Re: Re[2]: [VOTE] Accumulo 1.7.4-rc1
Posted by Keith Turner <ke...@deenlo.com>.
I successfully ran all test in 1.7.4rc1 that start with Kerberos,
except for KerberosRenewalIT which timed out after 541 secs. I am
going to try running KerberosRenewalIT in older 1.7 tags.
On Thu, Mar 22, 2018 at 3:20 PM, J. Mark Owens <jm...@gmail.com> wrote:
> I know that Christopher has been looking into the KerberosRenewalIT
> failures. Has anyone been having any additional issues with the Kerberos IT
> tests? I have been unsuccessful in getting through any of the four Kerberos
> related ITs.
>
> I've attempted to run each of the four Kerberos-related tests individually.
>
> KerberosIT tests fails with all 11 tests timing out after the allotted 5
> minutes per test.
> KerberosReplicationIT times out after 180 seconds.
> KerberosRenewalIT fails after 540 seconds.
> KerberosProxyIT is failing as well.
>
> I've been using the following command for the tests with the appropriate
> Kerberos IT proved for to the -Dit.test= argument.
>
> mvn clean verify -Dtest=NoSuchTestExists -Dit.test=KerberosIT
> -DfailIfNoTests=false
>
> Should I chalk it up to my testing setup not being robust enough to handle
> the tests or has anyone else experienced related failures?
>
>
>
>
> ------ Original Message ------
> From: "Mike Miller" <mi...@gmail.com>
> To: dev@accumulo.apache.org
> Cc: "Josh Elser" <el...@apache.org>
> Sent: 3/20/2018 4:02:32 PM
> Subject: Re: [VOTE] Accumulo 1.7.4-rc1
>
>> Well, just in case:
>> Verified sha1, md5 and asc signatures for binary and source tarballs:
>> gpg: Signature made Mon 19 Mar 2018 03:38:42 PM EDT
>> gpg: using RSA key 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D
>> gpg: Good signature from "Christopher L Tubbs II (Christopher) <
>> ctubbsii@gmail.com>" [unknown]
>> gpg: aka "Christopher L Tubbs II (Developer) <
>> ctubbsii@apache.org>" [unknown]
>> gpg: WARNING: This key is not certified with a trusted signature!
>> gpg: There is no indication that the signature belongs to the
>> owner.
>> Primary key fingerprint: 8CC4 F8A2 B29C 2B04 0F2B 835D 6F0C DAE7 00B6
>> 899D
>>
>>
>> On Tue, Mar 20, 2018 at 2:32 PM, Christopher <ct...@apache.org> wrote:
>>
>>> I'm currently looking at the KerberosRenewalIT failures that seem to be
>>> persisting across branches. From the logs, it looks like the accumulo
>>> services are trying to do ticket-cache based login renewals, instead of
>>> keytab-based renewals. This has been a problematic test for me before,
>>> and
>>> as such, I've gotten into the habit of ignoring it, but since I've not
>>> been
>>> able to get it to work on reruns, and it fails nearly 100% of the time
>>> (if
>>> not 100%) for me now, I decided to take a closer look. If it is doing
>>> ticket-cache based renewals, that could indicate a bug in the Kerberos
>>> authentication, and that would probably warrant a -1 from me... but I
>>> will
>>> continue to investigate first.
>>>
>>> Josh, you know more about the Kerberos stuff than anyone here, so if you
>>> have time/interest, I wouldn't mind getting your feedback on why this
>>> test
>>> might be failing for me.
>>>
>>> On Mon, Mar 19, 2018 at 3:44 PM Christopher <ct...@apache.org> wrote:
>>>
>>> > Accumulo Developers,
>>> >
>>> > Please consider the following candidate for Accumulo 1.7.4.
>>> >
>>> > Git Commit:
>>> > b2a59189108d736729432e81b3d5717000c6b891
>>> > Branch:
>>> > 1.7.4-rc1
>>> >
>>> > If this vote passes, a gpg-signed tag will be created using:
>>> > git tag -f -m 'Apache Accumulo 1.7.4' -s rel/1.7.4 \
>>> > b2a59189108d736729432e81b3d5717000c6b891
>>> >
>>> > Staging repo:
>>> > https://repository.apache.org/content/repositories/
>>> orgapacheaccumulo-1068
>>> > Source (official release artifact):
>>> > https://repository.apache.org/content/repositories/
>>> orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
>>> 4/accumulo-1.7.4-src.tar.gz
>>> > Binary:
>>> > https://repository.apache.org/content/repositories/
>>> orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
>>> 4/accumulo-1.7.4-bin.tar.gz
>>> > (Append ".sha1", ".md5", or ".asc" to download the signature/hash for a
>>> > given artifact.)
>>> >
>>> > All artifacts were built and staged with:
>>> > mvn release:prepare && mvn release:perform
>>> >
>>> > Signing keys are available at https://www.apache.org/dist/accumulo/KEYS
>>> > (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
>>> >
>>> > Release notes (in progress) can be found at:
>>> > https://accumulo.apache.org/release/accumulo-1.7.4/
>>> >
>>> > Please vote one of:
>>> > [ ] +1 - I have verified and accept...
>>> > [ ] +0 - I have reservations, but not strong enough to vote against...
>>> > [ ] -1 - Because..., I do not accept...
>>> > ... these artifacts as the 1.7.4 release of Apache Accumulo.
>>> >
>>> > This vote will remain open until at least Thu Mar 22 20:00:00 UTC 2018
>>> > (Thu Mar 22 16:00:00 EDT 2018 / Thu Mar 22 13:00:00 PDT 2018).
>>> > Voting continues until the release manager sends an email closing the
>>> vote.
>>> >
>>> > Thanks!
>>> >
>>> > P.S. Hint: download the whole staging repo with
>>> > wget -erobots=off -r -l inf -np -nH \
>>> >
>>> > https://repository.apache.org/content/repositories/
>>> orgapacheaccumulo-1068/
>>> > # note the trailing slash is needed
>>> >
>>> >
>>>
>
RE: Re[2]: [VOTE] Accumulo 1.7.4-rc1
Posted by Ed Coleman <de...@etcoleman.com>.
This is historical information from when I was running tests against 1.7.3, but in case it helps with the current discussion. (File timestamps are last Feb / March of 2107)
I was using local / openbox VM and spun up a small AWS instance. I never got KerberosRenewalIT.testReadAndWriteThroughTicketLifetime » TestTimedOut test ti... to pass.
All other tests passed at least once.
This is the chart that I kept to keep track – fingers crossed that is get through in a readable form. The X indicates the test failed.
Instance Type
Test
AWS1
AWS2
AW3
OpenBox 1
OpenBox 2
OpenBox3
AssignmentThreadsIT.testConcurrentAssignmentPerformance:91
x
x
x
BadDeleteMarkersCreatedIT>AccumuloClusterIT.teardownCluster:223 » TestTimedOut
x
ChaoticBalancerIT.test:80->Object.wait:502->Object.wait:-2 » TestTimedOut test...
x
x
ConditionalWriterIT.testTrace:1476 » TestTimedOut test timed out after 60 seco...
x
DurabilityIT.testWriteSpeed:103 log should be faster than flush
x
x
x
x
FateStarvationIT.run:79 » Runtime java.lang.RuntimeException: org.apache.zooke...
x
KerberosRenewalIT.testReadAndWriteThroughTicketLifetime » TestTimedOut test ti...
x
x
x
x
x
x
ShellServerIT.trace:1444
x
x
TabletStateChangeIteratorIT.test:100 No tables should need attention expected:<0> but was:<1>
x
x
UnorderedWorkAssignerReplicationIT.dataWasReplicatedToThePeerWithoutDrain:548 » TableOffline
KerberosReplicationIT.dataReplicatedToCorrectTable:224 » TestTimedOut test tim...
x
-----Original Message-----
From: J. Mark Owens [mailto:jmarkowe@gmail.com]
Sent: Thursday, March 22, 2018 3:20 PM
To: dev@accumulo.apache.org
Subject: Re[2]: [VOTE] Accumulo 1.7.4-rc1
I know that Christopher has been looking into the KerberosRenewalIT failures. Has anyone been having any additional issues with the Kerberos IT tests? I have been unsuccessful in getting through any of the four Kerberos related ITs.
I've attempted to run each of the four Kerberos-related tests individually.
KerberosIT tests fails with all 11 tests timing out after the allotted 5 minutes per test.
KerberosReplicationIT times out after 180 seconds.
KerberosRenewalIT fails after 540 seconds.
KerberosProxyIT is failing as well.
I've been using the following command for the tests with the appropriate Kerberos IT proved for to the -Dit.test= argument.
mvn clean verify -Dtest=NoSuchTestExists -Dit.test=KerberosIT -DfailIfNoTests=false
Should I chalk it up to my testing setup not being robust enough to handle the tests or has anyone else experienced related failures?
------ Original Message ------
From: "Mike Miller" < <ma...@gmail.com> michaelpmiller@gmail.com>
To: <ma...@accumulo.apache.org> dev@accumulo.apache.org
Cc: "Josh Elser" < <ma...@apache.org> elserj@apache.org>
Sent: 3/20/2018 4:02:32 PM
Subject: Re: [VOTE] Accumulo 1.7.4-rc1
>Well, just in case:
>Verified sha1, md5 and asc signatures for binary and source tarballs:
>gpg: Signature made Mon 19 Mar 2018 03:38:42 PM EDT
>gpg: using RSA key
>8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D
>gpg: Good signature from "Christopher L Tubbs II (Christopher) <
> <ma...@gmail.com> ctubbsii@gmail.com>" [unknown]
>gpg: aka "Christopher L Tubbs II (Developer) <
> <ma...@apache.org> ctubbsii@apache.org>" [unknown]
>gpg: WARNING: This key is not certified with a trusted signature!
>gpg: There is no indication that the signature belongs to the
>owner.
>Primary key fingerprint: 8CC4 F8A2 B29C 2B04 0F2B 835D 6F0C DAE7 00B6
>899D
>
>
>On Tue, Mar 20, 2018 at 2:32 PM, Christopher < <ma...@apache.org> ctubbsii@apache.org>
>wrote:
>
>>I'm currently looking at the KerberosRenewalIT failures that seem to
>>be
>>persisting across branches. From the logs, it looks like the accumulo
>>services are trying to do ticket-cache based login renewals, instead
>>of
>>keytab-based renewals. This has been a problematic test for me before,
>>and
>>as such, I've gotten into the habit of ignoring it, but since I've not
>>been
>>able to get it to work on reruns, and it fails nearly 100% of the time
>>(if
>>not 100%) for me now, I decided to take a closer look. If it is doing
>>ticket-cache based renewals, that could indicate a bug in the Kerberos
>>authentication, and that would probably warrant a -1 from me... but I
>>will
>>continue to investigate first.
>>
>>Josh, you know more about the Kerberos stuff than anyone here, so if
>>you
>>have time/interest, I wouldn't mind getting your feedback on why this
>>test
>>might be failing for me.
>>
>>On Mon, Mar 19, 2018 at 3:44 PM Christopher < <ma...@apache.org> ctubbsii@apache.org>
>>wrote:
>>
>> > Accumulo Developers,
>> >
>> > Please consider the following candidate for Accumulo 1.7.4.
>> >
>> > Git Commit:
>> > b2a59189108d736729432e81b3d5717000c6b891
>> > Branch:
>> > 1.7.4-rc1
>> >
>> > If this vote passes, a gpg-signed tag will be created using:
>> > git tag -f -m 'Apache Accumulo 1.7.4' -s rel/1.7.4 \
>> > b2a59189108d736729432e81b3d5717000c6b891
>> >
>> > Staging repo:
>> > <https://repository.apache.org/content/repositories/> https://repository.apache.org/content/repositories/
>>orgapacheaccumulo-1068
>> > Source (official release artifact):
>> > <https://repository.apache.org/content/repositories/> https://repository.apache.org/content/repositories/
>>orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
>>4/accumulo-1.7.4-src.tar.gz
>> > Binary:
>> > <https://repository.apache.org/content/repositories/> https://repository.apache.org/content/repositories/
>>orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
>>4/accumulo-1.7.4-bin.tar.gz
>> > (Append ".sha1", ".md5", or ".asc" to download the signature/hash
>>for a
>> > given artifact.)
>> >
>> > All artifacts were built and staged with:
>> > mvn release:prepare && mvn release:perform
>> >
>> > Signing keys are available at
>> <https://www.apache.org/dist/accumulo/KEYS> https://www.apache.org/dist/accumulo/KEYS
>> > (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
>> >
>> > Release notes (in progress) can be found at:
>> > <https://accumulo.apache.org/release/accumulo-1.7.4/> https://accumulo.apache.org/release/accumulo-1.7.4/
>> >
>> > Please vote one of:
>> > [ ] +1 - I have verified and accept...
>> > [ ] +0 - I have reservations, but not strong enough to vote
>>against...
>> > [ ] -1 - Because..., I do not accept...
>> > ... these artifacts as the 1.7.4 release of Apache Accumulo.
>> >
>> > This vote will remain open until at least Thu Mar 22 20:00:00 UTC
>>2018
>> > (Thu Mar 22 16:00:00 EDT 2018 / Thu Mar 22 13:00:00 PDT 2018).
>> > Voting continues until the release manager sends an email closing
>>the
>>vote.
>> >
>> > Thanks!
>> >
>> > P.S. Hint: download the whole staging repo with
>> > wget -erobots=off -r -l inf -np -nH \
>> >
>> > <https://repository.apache.org/content/repositories/> https://repository.apache.org/content/repositories/
>>orgapacheaccumulo-1068/
>> > # note the trailing slash is needed
>> >
>> >
>>
Re[2]: [VOTE] Accumulo 1.7.4-rc1
Posted by "J. Mark Owens" <jm...@gmail.com>.
I know that Christopher has been looking into the KerberosRenewalIT
failures. Has anyone been having any additional issues with the Kerberos
IT tests? I have been unsuccessful in getting through any of the four
Kerberos related ITs.
I've attempted to run each of the four Kerberos-related tests
individually.
KerberosIT tests fails with all 11 tests timing out after the allotted 5
minutes per test.
KerberosReplicationIT times out after 180 seconds.
KerberosRenewalIT fails after 540 seconds.
KerberosProxyIT is failing as well.
I've been using the following command for the tests with the appropriate
Kerberos IT proved for to the -Dit.test= argument.
mvn clean verify -Dtest=NoSuchTestExists -Dit.test=KerberosIT
-DfailIfNoTests=false
Should I chalk it up to my testing setup not being robust enough to
handle the tests or has anyone else experienced related failures?
------ Original Message ------
From: "Mike Miller" <mi...@gmail.com>
To: dev@accumulo.apache.org
Cc: "Josh Elser" <el...@apache.org>
Sent: 3/20/2018 4:02:32 PM
Subject: Re: [VOTE] Accumulo 1.7.4-rc1
>Well, just in case:
>Verified sha1, md5 and asc signatures for binary and source tarballs:
>gpg: Signature made Mon 19 Mar 2018 03:38:42 PM EDT
>gpg: using RSA key
>8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D
>gpg: Good signature from "Christopher L Tubbs II (Christopher) <
>ctubbsii@gmail.com>" [unknown]
>gpg: aka "Christopher L Tubbs II (Developer) <
>ctubbsii@apache.org>" [unknown]
>gpg: WARNING: This key is not certified with a trusted signature!
>gpg: There is no indication that the signature belongs to the
>owner.
>Primary key fingerprint: 8CC4 F8A2 B29C 2B04 0F2B 835D 6F0C DAE7 00B6
>899D
>
>
>On Tue, Mar 20, 2018 at 2:32 PM, Christopher <ct...@apache.org>
>wrote:
>
>>I'm currently looking at the KerberosRenewalIT failures that seem to
>>be
>>persisting across branches. From the logs, it looks like the accumulo
>>services are trying to do ticket-cache based login renewals, instead
>>of
>>keytab-based renewals. This has been a problematic test for me before,
>>and
>>as such, I've gotten into the habit of ignoring it, but since I've not
>>been
>>able to get it to work on reruns, and it fails nearly 100% of the time
>>(if
>>not 100%) for me now, I decided to take a closer look. If it is doing
>>ticket-cache based renewals, that could indicate a bug in the Kerberos
>>authentication, and that would probably warrant a -1 from me... but I
>>will
>>continue to investigate first.
>>
>>Josh, you know more about the Kerberos stuff than anyone here, so if
>>you
>>have time/interest, I wouldn't mind getting your feedback on why this
>>test
>>might be failing for me.
>>
>>On Mon, Mar 19, 2018 at 3:44 PM Christopher <ct...@apache.org>
>>wrote:
>>
>> > Accumulo Developers,
>> >
>> > Please consider the following candidate for Accumulo 1.7.4.
>> >
>> > Git Commit:
>> > b2a59189108d736729432e81b3d5717000c6b891
>> > Branch:
>> > 1.7.4-rc1
>> >
>> > If this vote passes, a gpg-signed tag will be created using:
>> > git tag -f -m 'Apache Accumulo 1.7.4' -s rel/1.7.4 \
>> > b2a59189108d736729432e81b3d5717000c6b891
>> >
>> > Staging repo:
>> > https://repository.apache.org/content/repositories/
>>orgapacheaccumulo-1068
>> > Source (official release artifact):
>> > https://repository.apache.org/content/repositories/
>>orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
>>4/accumulo-1.7.4-src.tar.gz
>> > Binary:
>> > https://repository.apache.org/content/repositories/
>>orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
>>4/accumulo-1.7.4-bin.tar.gz
>> > (Append ".sha1", ".md5", or ".asc" to download the signature/hash
>>for a
>> > given artifact.)
>> >
>> > All artifacts were built and staged with:
>> > mvn release:prepare && mvn release:perform
>> >
>> > Signing keys are available at
>>https://www.apache.org/dist/accumulo/KEYS
>> > (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
>> >
>> > Release notes (in progress) can be found at:
>> > https://accumulo.apache.org/release/accumulo-1.7.4/
>> >
>> > Please vote one of:
>> > [ ] +1 - I have verified and accept...
>> > [ ] +0 - I have reservations, but not strong enough to vote
>>against...
>> > [ ] -1 - Because..., I do not accept...
>> > ... these artifacts as the 1.7.4 release of Apache Accumulo.
>> >
>> > This vote will remain open until at least Thu Mar 22 20:00:00 UTC
>>2018
>> > (Thu Mar 22 16:00:00 EDT 2018 / Thu Mar 22 13:00:00 PDT 2018).
>> > Voting continues until the release manager sends an email closing
>>the
>>vote.
>> >
>> > Thanks!
>> >
>> > P.S. Hint: download the whole staging repo with
>> > wget -erobots=off -r -l inf -np -nH \
>> >
>> > https://repository.apache.org/content/repositories/
>>orgapacheaccumulo-1068/
>> > # note the trailing slash is needed
>> >
>> >
>>
Re: [VOTE] Accumulo 1.7.4-rc1
Posted by Mike Miller <mi...@gmail.com>.
Well, just in case:
Verified sha1, md5 and asc signatures for binary and source tarballs:
gpg: Signature made Mon 19 Mar 2018 03:38:42 PM EDT
gpg: using RSA key 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D
gpg: Good signature from "Christopher L Tubbs II (Christopher) <
ctubbsii@gmail.com>" [unknown]
gpg: aka "Christopher L Tubbs II (Developer) <
ctubbsii@apache.org>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the
owner.
Primary key fingerprint: 8CC4 F8A2 B29C 2B04 0F2B 835D 6F0C DAE7 00B6 899D
On Tue, Mar 20, 2018 at 2:32 PM, Christopher <ct...@apache.org> wrote:
> I'm currently looking at the KerberosRenewalIT failures that seem to be
> persisting across branches. From the logs, it looks like the accumulo
> services are trying to do ticket-cache based login renewals, instead of
> keytab-based renewals. This has been a problematic test for me before, and
> as such, I've gotten into the habit of ignoring it, but since I've not been
> able to get it to work on reruns, and it fails nearly 100% of the time (if
> not 100%) for me now, I decided to take a closer look. If it is doing
> ticket-cache based renewals, that could indicate a bug in the Kerberos
> authentication, and that would probably warrant a -1 from me... but I will
> continue to investigate first.
>
> Josh, you know more about the Kerberos stuff than anyone here, so if you
> have time/interest, I wouldn't mind getting your feedback on why this test
> might be failing for me.
>
> On Mon, Mar 19, 2018 at 3:44 PM Christopher <ct...@apache.org> wrote:
>
> > Accumulo Developers,
> >
> > Please consider the following candidate for Accumulo 1.7.4.
> >
> > Git Commit:
> > b2a59189108d736729432e81b3d5717000c6b891
> > Branch:
> > 1.7.4-rc1
> >
> > If this vote passes, a gpg-signed tag will be created using:
> > git tag -f -m 'Apache Accumulo 1.7.4' -s rel/1.7.4 \
> > b2a59189108d736729432e81b3d5717000c6b891
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/
> orgapacheaccumulo-1068
> > Source (official release artifact):
> > https://repository.apache.org/content/repositories/
> orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
> 4/accumulo-1.7.4-src.tar.gz
> > Binary:
> > https://repository.apache.org/content/repositories/
> orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
> 4/accumulo-1.7.4-bin.tar.gz
> > (Append ".sha1", ".md5", or ".asc" to download the signature/hash for a
> > given artifact.)
> >
> > All artifacts were built and staged with:
> > mvn release:prepare && mvn release:perform
> >
> > Signing keys are available at https://www.apache.org/dist/accumulo/KEYS
> > (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
> >
> > Release notes (in progress) can be found at:
> > https://accumulo.apache.org/release/accumulo-1.7.4/
> >
> > Please vote one of:
> > [ ] +1 - I have verified and accept...
> > [ ] +0 - I have reservations, but not strong enough to vote against...
> > [ ] -1 - Because..., I do not accept...
> > ... these artifacts as the 1.7.4 release of Apache Accumulo.
> >
> > This vote will remain open until at least Thu Mar 22 20:00:00 UTC 2018
> > (Thu Mar 22 16:00:00 EDT 2018 / Thu Mar 22 13:00:00 PDT 2018).
> > Voting continues until the release manager sends an email closing the
> vote.
> >
> > Thanks!
> >
> > P.S. Hint: download the whole staging repo with
> > wget -erobots=off -r -l inf -np -nH \
> >
> > https://repository.apache.org/content/repositories/
> orgapacheaccumulo-1068/
> > # note the trailing slash is needed
> >
> >
>
Re: [VOTE] Accumulo 1.7.4-rc1
Posted by Christopher <ct...@apache.org>.
I'm currently looking at the KerberosRenewalIT failures that seem to be
persisting across branches. From the logs, it looks like the accumulo
services are trying to do ticket-cache based login renewals, instead of
keytab-based renewals. This has been a problematic test for me before, and
as such, I've gotten into the habit of ignoring it, but since I've not been
able to get it to work on reruns, and it fails nearly 100% of the time (if
not 100%) for me now, I decided to take a closer look. If it is doing
ticket-cache based renewals, that could indicate a bug in the Kerberos
authentication, and that would probably warrant a -1 from me... but I will
continue to investigate first.
Josh, you know more about the Kerberos stuff than anyone here, so if you
have time/interest, I wouldn't mind getting your feedback on why this test
might be failing for me.
On Mon, Mar 19, 2018 at 3:44 PM Christopher <ct...@apache.org> wrote:
> Accumulo Developers,
>
> Please consider the following candidate for Accumulo 1.7.4.
>
> Git Commit:
> b2a59189108d736729432e81b3d5717000c6b891
> Branch:
> 1.7.4-rc1
>
> If this vote passes, a gpg-signed tag will be created using:
> git tag -f -m 'Apache Accumulo 1.7.4' -s rel/1.7.4 \
> b2a59189108d736729432e81b3d5717000c6b891
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1068
> Source (official release artifact):
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.4/accumulo-1.7.4-src.tar.gz
> Binary:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.4/accumulo-1.7.4-bin.tar.gz
> (Append ".sha1", ".md5", or ".asc" to download the signature/hash for a
> given artifact.)
>
> All artifacts were built and staged with:
> mvn release:prepare && mvn release:perform
>
> Signing keys are available at https://www.apache.org/dist/accumulo/KEYS
> (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
>
> Release notes (in progress) can be found at:
> https://accumulo.apache.org/release/accumulo-1.7.4/
>
> Please vote one of:
> [ ] +1 - I have verified and accept...
> [ ] +0 - I have reservations, but not strong enough to vote against...
> [ ] -1 - Because..., I do not accept...
> ... these artifacts as the 1.7.4 release of Apache Accumulo.
>
> This vote will remain open until at least Thu Mar 22 20:00:00 UTC 2018
> (Thu Mar 22 16:00:00 EDT 2018 / Thu Mar 22 13:00:00 PDT 2018).
> Voting continues until the release manager sends an email closing the vote.
>
> Thanks!
>
> P.S. Hint: download the whole staging repo with
> wget -erobots=off -r -l inf -np -nH \
>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1068/
> # note the trailing slash is needed
>
>
Re: [RESULT][VOTE] Accumulo 1.7.4-rc1
Posted by Christopher <ct...@apache.org>.
Oh, also, after those actions are done, archive the 1.7.3 release artifacts
and update relevant download links on website to point to archive (if not
automatic).
On Fri, Mar 23, 2018 at 7:49 PM Christopher <ct...@apache.org> wrote:
> Release actions performed:
>
> * Release Maven staging repo
> * Delete old staging repos
> * Publish artifacts to SVN dist area for mirrors (with SHA512 checksums)
> * Create signed tag rel/1.7.4
> * Merge tag into 1.8/master branches
> * Delete RC branches
> * Delete 1.7 maintenance branch (in anticipation of previously discussed
> expectation that 1.7.4 is likely last 1.7 release)
> * Updated release info at https://reporter.apache.org
> * Issued PR for updating website (includes updated apidocs, usermanual,
> doap, examples, and download page, and blog post draft removal):
> https://github.com/apache/accumulo-website/pull/68
>
> Remaining actions:
>
> * Update/merge PR for website, and rebuild website
> * Send announcement about release
>
>
> On Fri, Mar 23, 2018 at 5:44 PM Christopher <ct...@apache.org> wrote:
>
>> This vote passes with 4 +1s and no other votes.
>>
>> On Fri, Mar 23, 2018 at 5:31 PM Mike Walch <mw...@apache.org> wrote:
>>
>>> +1
>>>
>>> * Verified sha1 & md5 hashes matched
>>> * Verified signatures
>>> * Succesfully ran 1.7.4 binary locally using Uno
>>>
>>> On Mon, Mar 19, 2018 at 3:44 PM, Christopher <ct...@apache.org>
>>> wrote:
>>>
>>> > Accumulo Developers,
>>> >
>>> > Please consider the following candidate for Accumulo 1.7.4.
>>> >
>>> > Git Commit:
>>> > b2a59189108d736729432e81b3d5717000c6b891
>>> > Branch:
>>> > 1.7.4-rc1
>>> >
>>> > If this vote passes, a gpg-signed tag will be created using:
>>> > git tag -f -m 'Apache Accumulo 1.7.4' -s rel/1.7.4 \
>>> > b2a59189108d736729432e81b3d5717000c6b891
>>> >
>>> > Staging repo:
>>> >
>>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1068
>>> > Source (official release artifact):
>>> > https://repository.apache.org/content/repositories/
>>> > orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
>>> > 4/accumulo-1.7.4-src.tar.gz
>>> > Binary:
>>> > https://repository.apache.org/content/repositories/
>>> > orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
>>> > 4/accumulo-1.7.4-bin.tar.gz
>>> > (Append ".sha1", ".md5", or ".asc" to download the signature/hash for a
>>> > given artifact.)
>>> >
>>> > All artifacts were built and staged with:
>>> > mvn release:prepare && mvn release:perform
>>> >
>>> > Signing keys are available at
>>> https://www.apache.org/dist/accumulo/KEYS
>>> > (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
>>> >
>>> > Release notes (in progress) can be found at:
>>> > https://accumulo.apache.org/release/accumulo-1.7.4/
>>> >
>>> > Please vote one of:
>>> > [ ] +1 - I have verified and accept...
>>> > [ ] +0 - I have reservations, but not strong enough to vote against...
>>> > [ ] -1 - Because..., I do not accept...
>>> > ... these artifacts as the 1.7.4 release of Apache Accumulo.
>>> >
>>> > This vote will remain open until at least Thu Mar 22 20:00:00 UTC 2018
>>> > (Thu Mar 22 16:00:00 EDT 2018 / Thu Mar 22 13:00:00 PDT 2018).
>>> > Voting continues until the release manager sends an email closing the
>>> vote.
>>> >
>>> > Thanks!
>>> >
>>> > P.S. Hint: download the whole staging repo with
>>> > wget -erobots=off -r -l inf -np -nH \
>>> >
>>> >
>>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1068/
>>> > # note the trailing slash is needed
>>> >
>>>
>>
Re: [RESULT][VOTE] Accumulo 1.7.4-rc1
Posted by Christopher <ct...@apache.org>.
Release actions performed:
* Release Maven staging repo
* Delete old staging repos
* Publish artifacts to SVN dist area for mirrors (with SHA512 checksums)
* Create signed tag rel/1.7.4
* Merge tag into 1.8/master branches
* Delete RC branches
* Delete 1.7 maintenance branch (in anticipation of previously discussed
expectation that 1.7.4 is likely last 1.7 release)
* Updated release info at https://reporter.apache.org
* Issued PR for updating website (includes updated apidocs, usermanual,
doap, examples, and download page, and blog post draft removal):
https://github.com/apache/accumulo-website/pull/68
Remaining actions:
* Update/merge PR for website, and rebuild website
* Send announcement about release
On Fri, Mar 23, 2018 at 5:44 PM Christopher <ct...@apache.org> wrote:
> This vote passes with 4 +1s and no other votes.
>
> On Fri, Mar 23, 2018 at 5:31 PM Mike Walch <mw...@apache.org> wrote:
>
>> +1
>>
>> * Verified sha1 & md5 hashes matched
>> * Verified signatures
>> * Succesfully ran 1.7.4 binary locally using Uno
>>
>> On Mon, Mar 19, 2018 at 3:44 PM, Christopher <ct...@apache.org> wrote:
>>
>> > Accumulo Developers,
>> >
>> > Please consider the following candidate for Accumulo 1.7.4.
>> >
>> > Git Commit:
>> > b2a59189108d736729432e81b3d5717000c6b891
>> > Branch:
>> > 1.7.4-rc1
>> >
>> > If this vote passes, a gpg-signed tag will be created using:
>> > git tag -f -m 'Apache Accumulo 1.7.4' -s rel/1.7.4 \
>> > b2a59189108d736729432e81b3d5717000c6b891
>> >
>> > Staging repo:
>> >
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1068
>> > Source (official release artifact):
>> > https://repository.apache.org/content/repositories/
>> > orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
>> > 4/accumulo-1.7.4-src.tar.gz
>> > Binary:
>> > https://repository.apache.org/content/repositories/
>> > orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
>> > 4/accumulo-1.7.4-bin.tar.gz
>> > (Append ".sha1", ".md5", or ".asc" to download the signature/hash for a
>> > given artifact.)
>> >
>> > All artifacts were built and staged with:
>> > mvn release:prepare && mvn release:perform
>> >
>> > Signing keys are available at https://www.apache.org/dist/accumulo/KEYS
>> > (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
>> >
>> > Release notes (in progress) can be found at:
>> > https://accumulo.apache.org/release/accumulo-1.7.4/
>> >
>> > Please vote one of:
>> > [ ] +1 - I have verified and accept...
>> > [ ] +0 - I have reservations, but not strong enough to vote against...
>> > [ ] -1 - Because..., I do not accept...
>> > ... these artifacts as the 1.7.4 release of Apache Accumulo.
>> >
>> > This vote will remain open until at least Thu Mar 22 20:00:00 UTC 2018
>> > (Thu Mar 22 16:00:00 EDT 2018 / Thu Mar 22 13:00:00 PDT 2018).
>> > Voting continues until the release manager sends an email closing the
>> vote.
>> >
>> > Thanks!
>> >
>> > P.S. Hint: download the whole staging repo with
>> > wget -erobots=off -r -l inf -np -nH \
>> >
>> >
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1068/
>> > # note the trailing slash is needed
>> >
>>
>
[RESULT][VOTE] Accumulo 1.7.4-rc1
Posted by Christopher <ct...@apache.org>.
This vote passes with 4 +1s and no other votes.
On Fri, Mar 23, 2018 at 5:31 PM Mike Walch <mw...@apache.org> wrote:
> +1
>
> * Verified sha1 & md5 hashes matched
> * Verified signatures
> * Succesfully ran 1.7.4 binary locally using Uno
>
> On Mon, Mar 19, 2018 at 3:44 PM, Christopher <ct...@apache.org> wrote:
>
> > Accumulo Developers,
> >
> > Please consider the following candidate for Accumulo 1.7.4.
> >
> > Git Commit:
> > b2a59189108d736729432e81b3d5717000c6b891
> > Branch:
> > 1.7.4-rc1
> >
> > If this vote passes, a gpg-signed tag will be created using:
> > git tag -f -m 'Apache Accumulo 1.7.4' -s rel/1.7.4 \
> > b2a59189108d736729432e81b3d5717000c6b891
> >
> > Staging repo:
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1068
> > Source (official release artifact):
> > https://repository.apache.org/content/repositories/
> > orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
> > 4/accumulo-1.7.4-src.tar.gz
> > Binary:
> > https://repository.apache.org/content/repositories/
> > orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
> > 4/accumulo-1.7.4-bin.tar.gz
> > (Append ".sha1", ".md5", or ".asc" to download the signature/hash for a
> > given artifact.)
> >
> > All artifacts were built and staged with:
> > mvn release:prepare && mvn release:perform
> >
> > Signing keys are available at https://www.apache.org/dist/accumulo/KEYS
> > (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
> >
> > Release notes (in progress) can be found at:
> > https://accumulo.apache.org/release/accumulo-1.7.4/
> >
> > Please vote one of:
> > [ ] +1 - I have verified and accept...
> > [ ] +0 - I have reservations, but not strong enough to vote against...
> > [ ] -1 - Because..., I do not accept...
> > ... these artifacts as the 1.7.4 release of Apache Accumulo.
> >
> > This vote will remain open until at least Thu Mar 22 20:00:00 UTC 2018
> > (Thu Mar 22 16:00:00 EDT 2018 / Thu Mar 22 13:00:00 PDT 2018).
> > Voting continues until the release manager sends an email closing the
> vote.
> >
> > Thanks!
> >
> > P.S. Hint: download the whole staging repo with
> > wget -erobots=off -r -l inf -np -nH \
> >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1068/
> > # note the trailing slash is needed
> >
>
Re: [VOTE] Accumulo 1.7.4-rc1
Posted by Mike Walch <mw...@apache.org>.
+1
* Verified sha1 & md5 hashes matched
* Verified signatures
* Succesfully ran 1.7.4 binary locally using Uno
On Mon, Mar 19, 2018 at 3:44 PM, Christopher <ct...@apache.org> wrote:
> Accumulo Developers,
>
> Please consider the following candidate for Accumulo 1.7.4.
>
> Git Commit:
> b2a59189108d736729432e81b3d5717000c6b891
> Branch:
> 1.7.4-rc1
>
> If this vote passes, a gpg-signed tag will be created using:
> git tag -f -m 'Apache Accumulo 1.7.4' -s rel/1.7.4 \
> b2a59189108d736729432e81b3d5717000c6b891
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1068
> Source (official release artifact):
> https://repository.apache.org/content/repositories/
> orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
> 4/accumulo-1.7.4-src.tar.gz
> Binary:
> https://repository.apache.org/content/repositories/
> orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
> 4/accumulo-1.7.4-bin.tar.gz
> (Append ".sha1", ".md5", or ".asc" to download the signature/hash for a
> given artifact.)
>
> All artifacts were built and staged with:
> mvn release:prepare && mvn release:perform
>
> Signing keys are available at https://www.apache.org/dist/accumulo/KEYS
> (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
>
> Release notes (in progress) can be found at:
> https://accumulo.apache.org/release/accumulo-1.7.4/
>
> Please vote one of:
> [ ] +1 - I have verified and accept...
> [ ] +0 - I have reservations, but not strong enough to vote against...
> [ ] -1 - Because..., I do not accept...
> ... these artifacts as the 1.7.4 release of Apache Accumulo.
>
> This vote will remain open until at least Thu Mar 22 20:00:00 UTC 2018
> (Thu Mar 22 16:00:00 EDT 2018 / Thu Mar 22 13:00:00 PDT 2018).
> Voting continues until the release manager sends an email closing the vote.
>
> Thanks!
>
> P.S. Hint: download the whole staging repo with
> wget -erobots=off -r -l inf -np -nH \
>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1068/
> # note the trailing slash is needed
>
Re: [VOTE] Accumulo 1.7.4-rc1
Posted by Christopher <ct...@apache.org>.
+1 from me.
Found a minor problem with copyright dates:
Some of the copyright dates in NOTICE files in the tarballs and in the
generated html manual still indicate 2017 and should be updated, but I
don't think this is sufficient to block a release. (Please -1 if you
disagree; it is not a problem for me to fix and generate an rc2).
I also verified:
* All ITs pass in Jenkins (finally got KerberosRenewalIT to pass by setting
-Dhadoop.version=2.6.3)
* Source tarball contents match git commit sha1
* All hashes and signatures match
* Binary tarball contains expected libs and dependencies
* Jars are accompanied by javadoc and source jars
* Ran accumulo using https://github.com/astralway/uno and verified basic
install from binary tarball
* Inspected LICENSE/NOTICE files - see above for copyright date problem
On Thu, Mar 22, 2018 at 6:43 PM Mike Miller <mi...@gmail.com>
wrote:
> +1 Whoops forgot to vote in my earlier email.
>
> On Thu, Mar 22, 2018 at 6:41 PM, Keith Turner <ke...@deenlo.com> wrote:
>
> > +1
> >
> > Sigs and hashes looked good.
> > Ran Fluo ITs against staging repo
> > Also ran test on cluster against RC0
> >
> > I tried running KerberosRenewalIT against 1.7.1, 1.7.2, and 1.7.3. It
> > timed out in all branches. Test did not exist in 1.7.0.
> >
> > On Mon, Mar 19, 2018 at 3:44 PM, Christopher <ct...@apache.org>
> wrote:
> > > Accumulo Developers,
> > >
> > > Please consider the following candidate for Accumulo 1.7.4.
> > >
> > > Git Commit:
> > > b2a59189108d736729432e81b3d5717000c6b891
> > > Branch:
> > > 1.7.4-rc1
> > >
> > > If this vote passes, a gpg-signed tag will be created using:
> > > git tag -f -m 'Apache Accumulo 1.7.4' -s rel/1.7.4 \
> > > b2a59189108d736729432e81b3d5717000c6b891
> > >
> > > Staging repo:
> > > https://repository.apache.org/content/repositories/
> > orgapacheaccumulo-1068
> > > Source (official release artifact):
> > > https://repository.apache.org/content/repositories/
> > orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
> > 4/accumulo-1.7.4-src.tar.gz
> > > Binary:
> > > https://repository.apache.org/content/repositories/
> > orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
> > 4/accumulo-1.7.4-bin.tar.gz
> > > (Append ".sha1", ".md5", or ".asc" to download the signature/hash for a
> > > given artifact.)
> > >
> > > All artifacts were built and staged with:
> > > mvn release:prepare && mvn release:perform
> > >
> > > Signing keys are available at
> https://www.apache.org/dist/accumulo/KEYS
> > > (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
> > >
> > > Release notes (in progress) can be found at:
> > > https://accumulo.apache.org/release/accumulo-1.7.4/
> > >
> > > Please vote one of:
> > > [ ] +1 - I have verified and accept...
> > > [ ] +0 - I have reservations, but not strong enough to vote against...
> > > [ ] -1 - Because..., I do not accept...
> > > ... these artifacts as the 1.7.4 release of Apache Accumulo.
> > >
> > > This vote will remain open until at least Thu Mar 22 20:00:00 UTC 2018
> > > (Thu Mar 22 16:00:00 EDT 2018 / Thu Mar 22 13:00:00 PDT 2018).
> > > Voting continues until the release manager sends an email closing the
> > vote.
> > >
> > > Thanks!
> > >
> > > P.S. Hint: download the whole staging repo with
> > > wget -erobots=off -r -l inf -np -nH \
> > >
> > > https://repository.apache.org/content/repositories/
> > orgapacheaccumulo-1068/
> > > # note the trailing slash is needed
> >
>
Re: [VOTE] Accumulo 1.7.4-rc1
Posted by Mike Miller <mi...@gmail.com>.
+1 Whoops forgot to vote in my earlier email.
On Thu, Mar 22, 2018 at 6:41 PM, Keith Turner <ke...@deenlo.com> wrote:
> +1
>
> Sigs and hashes looked good.
> Ran Fluo ITs against staging repo
> Also ran test on cluster against RC0
>
> I tried running KerberosRenewalIT against 1.7.1, 1.7.2, and 1.7.3. It
> timed out in all branches. Test did not exist in 1.7.0.
>
> On Mon, Mar 19, 2018 at 3:44 PM, Christopher <ct...@apache.org> wrote:
> > Accumulo Developers,
> >
> > Please consider the following candidate for Accumulo 1.7.4.
> >
> > Git Commit:
> > b2a59189108d736729432e81b3d5717000c6b891
> > Branch:
> > 1.7.4-rc1
> >
> > If this vote passes, a gpg-signed tag will be created using:
> > git tag -f -m 'Apache Accumulo 1.7.4' -s rel/1.7.4 \
> > b2a59189108d736729432e81b3d5717000c6b891
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/
> orgapacheaccumulo-1068
> > Source (official release artifact):
> > https://repository.apache.org/content/repositories/
> orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
> 4/accumulo-1.7.4-src.tar.gz
> > Binary:
> > https://repository.apache.org/content/repositories/
> orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
> 4/accumulo-1.7.4-bin.tar.gz
> > (Append ".sha1", ".md5", or ".asc" to download the signature/hash for a
> > given artifact.)
> >
> > All artifacts were built and staged with:
> > mvn release:prepare && mvn release:perform
> >
> > Signing keys are available at https://www.apache.org/dist/accumulo/KEYS
> > (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
> >
> > Release notes (in progress) can be found at:
> > https://accumulo.apache.org/release/accumulo-1.7.4/
> >
> > Please vote one of:
> > [ ] +1 - I have verified and accept...
> > [ ] +0 - I have reservations, but not strong enough to vote against...
> > [ ] -1 - Because..., I do not accept...
> > ... these artifacts as the 1.7.4 release of Apache Accumulo.
> >
> > This vote will remain open until at least Thu Mar 22 20:00:00 UTC 2018
> > (Thu Mar 22 16:00:00 EDT 2018 / Thu Mar 22 13:00:00 PDT 2018).
> > Voting continues until the release manager sends an email closing the
> vote.
> >
> > Thanks!
> >
> > P.S. Hint: download the whole staging repo with
> > wget -erobots=off -r -l inf -np -nH \
> >
> > https://repository.apache.org/content/repositories/
> orgapacheaccumulo-1068/
> > # note the trailing slash is needed
>
Re: [VOTE] Accumulo 1.7.4-rc1
Posted by Keith Turner <ke...@deenlo.com>.
+1
Sigs and hashes looked good.
Ran Fluo ITs against staging repo
Also ran test on cluster against RC0
I tried running KerberosRenewalIT against 1.7.1, 1.7.2, and 1.7.3. It
timed out in all branches. Test did not exist in 1.7.0.
On Mon, Mar 19, 2018 at 3:44 PM, Christopher <ct...@apache.org> wrote:
> Accumulo Developers,
>
> Please consider the following candidate for Accumulo 1.7.4.
>
> Git Commit:
> b2a59189108d736729432e81b3d5717000c6b891
> Branch:
> 1.7.4-rc1
>
> If this vote passes, a gpg-signed tag will be created using:
> git tag -f -m 'Apache Accumulo 1.7.4' -s rel/1.7.4 \
> b2a59189108d736729432e81b3d5717000c6b891
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1068
> Source (official release artifact):
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.4/accumulo-1.7.4-src.tar.gz
> Binary:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.4/accumulo-1.7.4-bin.tar.gz
> (Append ".sha1", ".md5", or ".asc" to download the signature/hash for a
> given artifact.)
>
> All artifacts were built and staged with:
> mvn release:prepare && mvn release:perform
>
> Signing keys are available at https://www.apache.org/dist/accumulo/KEYS
> (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
>
> Release notes (in progress) can be found at:
> https://accumulo.apache.org/release/accumulo-1.7.4/
>
> Please vote one of:
> [ ] +1 - I have verified and accept...
> [ ] +0 - I have reservations, but not strong enough to vote against...
> [ ] -1 - Because..., I do not accept...
> ... these artifacts as the 1.7.4 release of Apache Accumulo.
>
> This vote will remain open until at least Thu Mar 22 20:00:00 UTC 2018
> (Thu Mar 22 16:00:00 EDT 2018 / Thu Mar 22 13:00:00 PDT 2018).
> Voting continues until the release manager sends an email closing the vote.
>
> Thanks!
>
> P.S. Hint: download the whole staging repo with
> wget -erobots=off -r -l inf -np -nH \
>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1068/
> # note the trailing slash is needed