You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Andrii Tkach (JIRA)" <ji...@apache.org> on 2018/12/04 13:38:00 UTC

[jira] [Commented] (AMBARI-24989) Knox: Reorder of query parameters breaks Ambari logic for retrieving configs

    [ https://issues.apache.org/jira/browse/AMBARI-24989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708710#comment-16708710 ] 

Andrii Tkach commented on AMBARI-24989:
---------------------------------------

committed to trunk

> Knox: Reorder of query parameters breaks Ambari logic for retrieving configs
> ----------------------------------------------------------------------------
>
>                 Key: AMBARI-24989
>                 URL: https://issues.apache.org/jira/browse/AMBARI-24989
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.7.3
>            Reporter: Andrii Tkach
>            Assignee: Andrii Tkach
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 2.8.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Knox proxy sometimes modifies service config version request during transferring.
> I extended logging on the ambari server to track actual requests. 
> Direct API request:
> {noformat}
> https://172.27.16.232:8443/api/v1/clusters/cl1/configurations/service_config_versions?
> service_name=HBASE&service_config_version.in(12)%7C
> service_name.in(ATLAS,YARN,RANGER,HIVE,HDFS,MAPREDUCE2,SPARK2,TEZ,DRUID,ZOOKEEPER,AMBARI_METRICS,KAFKA,RANGER_KMS)&is_current=true&_=1542046206583
> {noformat}
> Via Knox:
> {noformat}
> https://ctr-e138-1518143905142-579999-01-000002.hwx.site/api/v1/clusters/cl1/configurations/service_config_versions?
> service_name=HBASE&is_current=true&service_config_version.in(12)%7C
> service_name.in(ATLAS,YARN,RANGER,HIVE,HDFS,MAPREDUCE2,SPARK2,TEZ,DRUID,ZOOKEEPER,AMBARI_METRICS,KAFKA,RANGER_KMS)&_=1542046206583
> {noformat}
> In both cases same request was used on client side:
> {noformat}
> /api/v1/clusters/cl1/configurations/service_config_versions?
> service_name=HBASE&service_config_version.in(12)|
> service_name.in(ATLAS,YARN,RANGER,HIVE,HDFS,MAPREDUCE2,SPARK2,TEZ,DRUID,ZOOKEEPER,AMBARI_METRICS,KAFKA,RANGER_KMS)&is_current=true&_=1542046206583
> {noformat}
> As we can see Knox proxy reordered request parameters (is_current=true was moved) and completely changed request logic.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)