[AMBARI-5162] Mirroring: surface error messages from Falcon

• Type: Task
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.5.1
• Fix Version/s: 1.5.1
• Component/s: ambari-web
• Assignee: Aleksandr Kovalenko
• Reporter: Aleksandr Kovalenko
• Created: 20/Mar/14 16:27
• Updated: 20/Mar/14 16:32
• Resolved: 20/Mar/14 16:32

Description

When errors are encountered, depending on the API call made:
1. An error popup shows "Bad Request" and nothing else. Falcon API is indeed returning error details, so we should show that. For example, entering an invalid Oozie URL shows the following:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><result><status>FAILED</status><message>Invalid Workflow server or port: http://yusakum2-2.c.pramod-thangali.internal:11000
Unable to reach Oozie server.</message><requestId>2e8320b4-7327-4278-99de-2292456a27c0</requestId></result>

2. No error popup is shown at all. I believe this happens when "submitAndSchedule"'s schedule part fails (not 100%, please confirm). In my case "hadoop.proxyuser.falcon.hosts" was set to the Falcon server host name, which won't work when mirroring data across clusters. Maybe set this to something invalid and see if this can be replicated in a single cluster environment.
The API error message was:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><result><status>FAILED</status><message>Unable to create retention workflow
Unauthorized connection for super-user: falcon from IP 10.240.114.245</message><requestId>ed258530-617a-4b77-bab3-508f9cdd8eb9</requestId></result>