Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
2.7.3
Description
Knox proxy sometimes modifies service config version request during transferring.
I extended logging on the ambari server to track actual requests.
Direct API request:
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
Via Knox:
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
In both cases same request was used on client side:
/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
As we can see Knox proxy reordered request parameters (is_current=true was moved) and completely changed request logic.
Attachments
Issue Links
- links to