question Re: Ambari 2.6.3.1 using WFM // service check remote API failed in Support Questions

Ambari 2.6.3.1 using WFM // service check remote API failed

w3109ww — Wed, 17 Oct 2018 17:13:51 GMT

I created an instance because I wanted to use WFM

all setting opt default

but when i using WFM

'Process Check' does not proceed

& i see 'remote API failed'

help me

+++ Kerberos security is disabled

Re: Ambari 2.6.3.1 using WFM // service check remote API failed

JonathanSneep — Wed, 17 Oct 2018 17:25:14 GMT

@Jung Heedong

Are you using Knox by any chance?

Re: Ambari 2.6.3.1 using WFM // service check remote API failed

w3109ww — Wed, 17 Oct 2018 18:07:14 GMT

YES YES using KNOX , RANGER

Re: Ambari 2.6.3.1 using WFM // service check remote API failed

JonathanSneep — Wed, 17 Oct 2018 18:10:11 GMT

@Jung Heedong
Does accessing the workflow manager view work OK when you're bypassing knox and accessing via ambari directly?
You may be running into a known issue, regarding WFM which results in the 'remote API failed' error if accessed through knox. This is resolved in HDP 3.

Re: Ambari 2.6.3.1 using WFM // service check remote API failed

w3109ww — Wed, 17 Oct 2018 18:13:01 GMT

Could you let me know the commit ID?

Re: Ambari 2.6.3.1 using WFM // service check remote API failed

w3109ww — Wed, 17 Oct 2018 18:14:45 GMT

Does accessing the workflow manager view work OK when you're bypassing knox and accessing via ambari directly? : Possible!

Re: Ambari 2.6.3.1 using WFM // service check remote API failed

w3109ww — Wed, 17 Oct 2018 18:16:01 GMT

I am in a situation where I need to use KNOX in ambari hdp2.0 environment

Re: Ambari 2.6.3.1 using WFM // service check remote API failed

JonathanSneep — Wed, 17 Oct 2018 19:18:23 GMT

@Jung Heedong

Please refer to this JIRA:

https://issues.apache.org/jira/browse/KNOX-1074

You can try the following workaround, if you are unable to upgrade by making changes in service.xml and rewrite.xml.
You'd find these at

/var/lib/knox/data-<yourHDPversion>/services/ambariui/2.2.0/service.xml 
/var/lib/knox/data-<yourHDPversion>/services/ambariui/2.2.0/rewrite.xml

Add the following rule in service.xml

<route path="/ambari/api/v1/views/WORKFLOW_MANAGER/versions/**/instances/testwfm/resources/proxy/**"> <rewrite apply="AMBARI/ambari/api/outbound/workflowmanager" to="response.body"/> 
</route>

And a rule in rewrite.xml

<filter name="AMBARI/ambari/api/outbound/workflowmanager"> 
<content type="text/plain" asType="text/xml"> 
</content> 
</filter>

(restart knox afterwards)

Please take a moment to click accept answer, if this helped you. It will help others find the solution quickly, when looking for the same issue online.

Re: Ambari 2.6.3.1 using WFM // service check remote API failed

w3109ww — Wed, 17 Oct 2018 19:37:53 GMT

Thanks for your help. I cant try now but it was a big help. Can I ask you again if I have a problem?

Re: Ambari 2.6.3.1 using WFM // service check remote API failed

JonathanSneep — Wed, 17 Oct 2018 19:40:10 GMT

@Jung Heedong

Of course, it may be best to start a new post if you still have any issues, as it will have better visibility. You can tag users (ex. me) in posts by typing '@' followed by their username. That way we get notified when you post 🙂