You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by Duo Zhang <zh...@apache.org> on 2018/01/16 10:38:11 UTC
PreCommit-Admin fails to fetch issue list from jira
Started from this build
https://builds.apache.org/job/PreCommit-Admin/329113/
Have dug a bit, it seems that now jira does not allow our query to be run
by unauthorized user, you will get a 400 if you do not login. This is the
error page when accessing
https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-xml/12323182/SearchRequest-12323182.xml?tempMax=50
HTTP Status 400 - A value with ID '12315621' does not exist for the field
'project'.
*type* Status report
*message* *A value with ID '12315621' does not exist for the field
'project'.*
*description* *The request sent by the client was syntactically incorrect.*
------------------------------
Apache Tomcat/8.5.6
The project '12315621 ' is Ranger. I do not have the permission to modify
the original filter, and do not have the permission to create a public
filter either. So for me there is no way to fix the problem.
Could the Ranger project check if you have changed some permission configs?
Or could someone who has the permission to create public filters creates a
new filter without Ranger to see if it works? There are plenty of projects
which rely on the PreCommit-Admin job.
Thanks.
Re: PreCommit-Admin fails to fetch issue list from jira
Posted by Allen Wittenauer <aw...@effectivemachines.com>.
> On Jan 16, 2018, at 1:41 PM, Vihang Karajgaonkar <vi...@cloudera.com> wrote:
>
> yes, thats correct. I had created https://issues.apache.org/jira/browse/INFRA-15849 to get that fixed. But looks like based on the comment there we need to modify that job to use REST instead of SOAP?
I think there is some confusion. There are two parts in play.
The SOAP API is (or was, depending upon which fork we’re talking about) used to talk to JIRA to write comments. That’s only used by older strains of test-patch. Some versions have replaced it with REST calls. [For the record, Apache Yetus replaced that code with REST calls years ago in one of the first set of patches.] FWIW, it’s been documented by Atlassian that SOAP was going to go away for quite a while.
precommit-admin uses raw HTTP calls. The problem with it is that the URLs it is using for JIRA now require authentication. The patch I’ve posted in YETUS-594 includes adding support to auth against those URLs.
> Do we know who owns that job?
In the case of test-patch, again, it depends upon the strain. Most of the heavy hitters (Hadoop, HBase, Hive, Avro, Accumulo, … lucene and solr are in progress… umm… sure I’m missing some ) have switched over to using Apache Yetus instead of keeping a local copy. This way resources can be shared and work pooled together. It is getting updated fairly regularly.
in the case of precommit-admin, technically it’s Hadoop. But it is effectively no one since the branch it comes from doesn’t even exist in git. (It’s still pulled from svn) Post-YETUS-594, however, I’m planning on dropping a note to builds@ and switch precommit-admin over to come from Apache Yetus where it will actually get some attention.
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: PreCommit-Admin fails to fetch issue list from jira
Posted by Vihang Karajgaonkar <vi...@cloudera.com>.
yes, thats correct. I had created
https://issues.apache.org/jira/browse/INFRA-15849 to get that fixed. But
looks like based on the comment there we need to modify that job to use
REST instead of SOAP? Do we know who owns that job?
On Tue, Jan 16, 2018 at 1:35 PM, Allen Wittenauer <aw...@effectivemachines.com>
wrote:
>
> > On Jan 16, 2018, at 1:27 PM, Vihang Karajgaonkar <vi...@cloudera.com>
> wrote:
> >
> > Hive pre-commit jobs are broken as well since the JIRA upgrade. Did you
> have to make any changes to hadoop-precommit job to make it work? Any
> pointers will help us fix ours as well.
>
> Until precommit-admin gets fixed, no one is getting automated JIRA
> testing.
>
>
Re: PreCommit-Admin fails to fetch issue list from jira
Posted by Allen Wittenauer <aw...@effectivemachines.com>.
> On Jan 16, 2018, at 1:27 PM, Vihang Karajgaonkar <vi...@cloudera.com> wrote:
>
> Hive pre-commit jobs are broken as well since the JIRA upgrade. Did you have to make any changes to hadoop-precommit job to make it work? Any pointers will help us fix ours as well.
Until precommit-admin gets fixed, no one is getting automated JIRA testing.
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: PreCommit-Admin fails to fetch issue list from jira
Posted by Vihang Karajgaonkar <vi...@cloudera.com>.
Hive pre-commit jobs are broken as well since the JIRA upgrade. Did you
have to make any changes to hadoop-precommit job to make it work? Any
pointers will help us fix ours as well.
Thanks.
On Tue, Jan 16, 2018 at 9:06 AM, Allen Wittenauer <aw...@effectivemachines.com>
wrote:
>
> FWIW, the new JIRA has broken a few things thus far. Akira fixed an issue
> with test-patch and I’ve got a fix for precommit-admin as part of
> YETUS-594. As soon as it and YETUS-592 gets a review+commit, I’ll start
> the 0.7.0 release process.
>
> Also, as a reminder, Apache Yetus uses +1’s from contributors as commit
> votes if anyone would like to help...
>
> > On Jan 16, 2018, at 3:36 AM, Steve Loughran <st...@hortonworks.com>
> wrote:
> >
> > There's been a JIRA update. Ask at infra@apache.org ; they may have
> locked it down more
> >
> >> On 16 Jan 2018, at 10:38, Duo Zhang <zh...@apache.org> wrote:
> >>
> >> Started from this build
> >>
> >> https://builds.apache.org/job/PreCommit-Admin/329113/
> >>
> >> Have dug a bit, it seems that now jira does not allow our query to be
> run
> >> by unauthorized user, you will get a 400 if you do not login. This is
> the
> >> error page when accessing
> >>
> >> https://issues.apache.org/jira/sr/jira.issueviews:
> searchrequest-xml/12323182/SearchRequest-12323182.xml?tempMax=50
> >> HTTP Status 400 - A value with ID '12315621' does not exist for the
> field
> >> 'project'.
> >>
> >> *type* Status report
> >>
> >> *message* *A value with ID '12315621' does not exist for the field
> >> 'project'.*
> >>
> >> *description* *The request sent by the client was syntactically
> incorrect.*
> >> ------------------------------
> >> Apache Tomcat/8.5.6
> >>
> >> The project '12315621 ' is Ranger. I do not have the permission to
> modify
> >> the original filter, and do not have the permission to create a public
> >> filter either. So for me there is no way to fix the problem.
> >>
> >> Could the Ranger project check if you have changed some permission
> configs?
> >> Or could someone who has the permission to create public filters
> creates a
> >> new filter without Ranger to see if it works? There are plenty of
> projects
> >> which rely on the PreCommit-Admin job.
> >>
> >> Thanks.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>
Re: PreCommit-Admin fails to fetch issue list from jira
Posted by Allen Wittenauer <aw...@effectivemachines.com>.
FWIW, the new JIRA has broken a few things thus far. Akira fixed an issue with test-patch and I’ve got a fix for precommit-admin as part of YETUS-594. As soon as it and YETUS-592 gets a review+commit, I’ll start the 0.7.0 release process.
Also, as a reminder, Apache Yetus uses +1’s from contributors as commit votes if anyone would like to help...
> On Jan 16, 2018, at 3:36 AM, Steve Loughran <st...@hortonworks.com> wrote:
>
> There's been a JIRA update. Ask at infra@apache.org ; they may have locked it down more
>
>> On 16 Jan 2018, at 10:38, Duo Zhang <zh...@apache.org> wrote:
>>
>> Started from this build
>>
>> https://builds.apache.org/job/PreCommit-Admin/329113/
>>
>> Have dug a bit, it seems that now jira does not allow our query to be run
>> by unauthorized user, you will get a 400 if you do not login. This is the
>> error page when accessing
>>
>> https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-xml/12323182/SearchRequest-12323182.xml?tempMax=50
>> HTTP Status 400 - A value with ID '12315621' does not exist for the field
>> 'project'.
>>
>> *type* Status report
>>
>> *message* *A value with ID '12315621' does not exist for the field
>> 'project'.*
>>
>> *description* *The request sent by the client was syntactically incorrect.*
>> ------------------------------
>> Apache Tomcat/8.5.6
>>
>> The project '12315621 ' is Ranger. I do not have the permission to modify
>> the original filter, and do not have the permission to create a public
>> filter either. So for me there is no way to fix the problem.
>>
>> Could the Ranger project check if you have changed some permission configs?
>> Or could someone who has the permission to create public filters creates a
>> new filter without Ranger to see if it works? There are plenty of projects
>> which rely on the PreCommit-Admin job.
>>
>> Thanks.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: PreCommit-Admin fails to fetch issue list from jira
Posted by Steve Loughran <st...@hortonworks.com>.
There's been a JIRA update. Ask at infra@apache.org ; they may have locked it down more
> On 16 Jan 2018, at 10:38, Duo Zhang <zh...@apache.org> wrote:
>
> Started from this build
>
> https://builds.apache.org/job/PreCommit-Admin/329113/
>
> Have dug a bit, it seems that now jira does not allow our query to be run
> by unauthorized user, you will get a 400 if you do not login. This is the
> error page when accessing
>
> https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-xml/12323182/SearchRequest-12323182.xml?tempMax=50
> HTTP Status 400 - A value with ID '12315621' does not exist for the field
> 'project'.
>
> *type* Status report
>
> *message* *A value with ID '12315621' does not exist for the field
> 'project'.*
>
> *description* *The request sent by the client was syntactically incorrect.*
> ------------------------------
> Apache Tomcat/8.5.6
>
> The project '12315621 ' is Ranger. I do not have the permission to modify
> the original filter, and do not have the permission to create a public
> filter either. So for me there is no way to fix the problem.
>
> Could the Ranger project check if you have changed some permission configs?
> Or could someone who has the permission to create public filters creates a
> new filter without Ranger to see if it works? There are plenty of projects
> which rely on the PreCommit-Admin job.
>
> Thanks.
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: PreCommit-Admin fails to fetch issue list from jira
Posted by "张铎 (Duo Zhang)" <pa...@gmail.com>.
I've voted a +1 on the issue. Great work.
Let's make the PreCommit-Admin work again ASAP.
Thanks.
2018-01-17 5:43 GMT+08:00 Sean Busbey <bu...@apache.org>:
> FYI Duo, I believe
>
> https://issues.apache.org/jira/browse/YETUS-594
>
> is also slated to fix this. it just needs a review.
>
> On Tue, Jan 16, 2018 at 4:38 AM, Duo Zhang <zh...@apache.org> wrote:
> > Started from this build
> >
> > https://builds.apache.org/job/PreCommit-Admin/329113/
> >
> > Have dug a bit, it seems that now jira does not allow our query to be run
> > by unauthorized user, you will get a 400 if you do not login. This is the
> > error page when accessing
> >
> > https://issues.apache.org/jira/sr/jira.issueviews:
> searchrequest-xml/12323182/SearchRequest-12323182.xml?tempMax=50
> > HTTP Status 400 - A value with ID '12315621' does not exist for the field
> > 'project'.
> >
> > *type* Status report
> >
> > *message* *A value with ID '12315621' does not exist for the field
> > 'project'.*
> >
> > *description* *The request sent by the client was syntactically
> incorrect.*
> > ------------------------------
> > Apache Tomcat/8.5.6
> >
> > The project '12315621 ' is Ranger. I do not have the permission to modify
> > the original filter, and do not have the permission to create a public
> > filter either. So for me there is no way to fix the problem.
> >
> > Could the Ranger project check if you have changed some permission
> configs?
> > Or could someone who has the permission to create public filters creates
> a
> > new filter without Ranger to see if it works? There are plenty of
> projects
> > which rely on the PreCommit-Admin job.
> >
> > Thanks.
>
Re: PreCommit-Admin fails to fetch issue list from jira
Posted by Sean Busbey <bu...@apache.org>.
FYI Duo, I believe
https://issues.apache.org/jira/browse/YETUS-594
is also slated to fix this. it just needs a review.
On Tue, Jan 16, 2018 at 4:38 AM, Duo Zhang <zh...@apache.org> wrote:
> Started from this build
>
> https://builds.apache.org/job/PreCommit-Admin/329113/
>
> Have dug a bit, it seems that now jira does not allow our query to be run
> by unauthorized user, you will get a 400 if you do not login. This is the
> error page when accessing
>
> https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-xml/12323182/SearchRequest-12323182.xml?tempMax=50
> HTTP Status 400 - A value with ID '12315621' does not exist for the field
> 'project'.
>
> *type* Status report
>
> *message* *A value with ID '12315621' does not exist for the field
> 'project'.*
>
> *description* *The request sent by the client was syntactically incorrect.*
> ------------------------------
> Apache Tomcat/8.5.6
>
> The project '12315621 ' is Ranger. I do not have the permission to modify
> the original filter, and do not have the permission to create a public
> filter either. So for me there is no way to fix the problem.
>
> Could the Ranger project check if you have changed some permission configs?
> Or could someone who has the permission to create public filters creates a
> new filter without Ranger to see if it works? There are plenty of projects
> which rely on the PreCommit-Admin job.
>
> Thanks.
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: PreCommit-Admin fails to fetch issue list from jira
Posted by Sean Busbey <bu...@apache.org>.
FYI Duo, I believe
https://issues.apache.org/jira/browse/YETUS-594
is also slated to fix this. it just needs a review.
On Tue, Jan 16, 2018 at 4:38 AM, Duo Zhang <zh...@apache.org> wrote:
> Started from this build
>
> https://builds.apache.org/job/PreCommit-Admin/329113/
>
> Have dug a bit, it seems that now jira does not allow our query to be run
> by unauthorized user, you will get a 400 if you do not login. This is the
> error page when accessing
>
> https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-xml/12323182/SearchRequest-12323182.xml?tempMax=50
> HTTP Status 400 - A value with ID '12315621' does not exist for the field
> 'project'.
>
> *type* Status report
>
> *message* *A value with ID '12315621' does not exist for the field
> 'project'.*
>
> *description* *The request sent by the client was syntactically incorrect.*
> ------------------------------
> Apache Tomcat/8.5.6
>
> The project '12315621 ' is Ranger. I do not have the permission to modify
> the original filter, and do not have the permission to create a public
> filter either. So for me there is no way to fix the problem.
>
> Could the Ranger project check if you have changed some permission configs?
> Or could someone who has the permission to create public filters creates a
> new filter without Ranger to see if it works? There are plenty of projects
> which rely on the PreCommit-Admin job.
>
> Thanks.
Re: PreCommit-Admin fails to fetch issue list from jira
Posted by Sean Busbey <bu...@apache.org>.
FYI Duo, I believe
https://issues.apache.org/jira/browse/YETUS-594
is also slated to fix this. it just needs a review.
On Tue, Jan 16, 2018 at 4:38 AM, Duo Zhang <zh...@apache.org> wrote:
> Started from this build
>
> https://builds.apache.org/job/PreCommit-Admin/329113/
>
> Have dug a bit, it seems that now jira does not allow our query to be run
> by unauthorized user, you will get a 400 if you do not login. This is the
> error page when accessing
>
> https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-xml/12323182/SearchRequest-12323182.xml?tempMax=50
> HTTP Status 400 - A value with ID '12315621' does not exist for the field
> 'project'.
>
> *type* Status report
>
> *message* *A value with ID '12315621' does not exist for the field
> 'project'.*
>
> *description* *The request sent by the client was syntactically incorrect.*
> ------------------------------
> Apache Tomcat/8.5.6
>
> The project '12315621 ' is Ranger. I do not have the permission to modify
> the original filter, and do not have the permission to create a public
> filter either. So for me there is no way to fix the problem.
>
> Could the Ranger project check if you have changed some permission configs?
> Or could someone who has the permission to create public filters creates a
> new filter without Ranger to see if it works? There are plenty of projects
> which rely on the PreCommit-Admin job.
>
> Thanks.
Re: PreCommit-Admin fails to fetch issue list from jira
Posted by Sean Busbey <bu...@apache.org>.
FYI Duo, I believe
https://issues.apache.org/jira/browse/YETUS-594
is also slated to fix this. it just needs a review.
On Tue, Jan 16, 2018 at 4:38 AM, Duo Zhang <zh...@apache.org> wrote:
> Started from this build
>
> https://builds.apache.org/job/PreCommit-Admin/329113/
>
> Have dug a bit, it seems that now jira does not allow our query to be run
> by unauthorized user, you will get a 400 if you do not login. This is the
> error page when accessing
>
> https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-xml/12323182/SearchRequest-12323182.xml?tempMax=50
> HTTP Status 400 - A value with ID '12315621' does not exist for the field
> 'project'.
>
> *type* Status report
>
> *message* *A value with ID '12315621' does not exist for the field
> 'project'.*
>
> *description* *The request sent by the client was syntactically incorrect.*
> ------------------------------
> Apache Tomcat/8.5.6
>
> The project '12315621 ' is Ranger. I do not have the permission to modify
> the original filter, and do not have the permission to create a public
> filter either. So for me there is no way to fix the problem.
>
> Could the Ranger project check if you have changed some permission configs?
> Or could someone who has the permission to create public filters creates a
> new filter without Ranger to see if it works? There are plenty of projects
> which rely on the PreCommit-Admin job.
>
> Thanks.