FALCON-2033 ProcessRerun tests fail with User [falcon] not authorized for Coord job #193
Conversation
|
+1. Better to have a UT or IT for rerun. Could be a separate JIRA :) |
| @@ -1015,7 +1018,7 @@ private String getConsoleUrl(String cluster, String actionId) throws FalconExcep | |||
| // Get conf when workflow is launched. | |||
| if (coordinatorAction.getExternalId() != null) { | |||
| WorkflowJob jobInfo = client.getJobInfo(coordinatorAction.getExternalId()); | |||
|
|
|||
| workflowUser = jobInfo.getUser(); | |||
There was a problem hiding this comment.
If you look at AbstractRerunConsumer it's already taken care of
// Login the user to access WfEngine as this user
CurrentUser.authenticate(message.getWorkflowUser());
There was a problem hiding this comment.
Interesting. Does the message contain the correct workflow user?
From the log, the user for rerun used to be "falcon". Balu's change corrects it.
There was a problem hiding this comment.
Thank you @sowmyaramesh and @yzheng-hortonworks for raising valid points. From the logs reported by @muraliramasami , the rerun user is falcon when the coordinator (thus the workflow) were by user "hrt_qa". So CurrentUser.authenticate(message.getWorkflowUser()) is supposed to work and run re-run as message.getWorkflowUser(), but it is not accurate anymore. Let me debug some more.
There was a problem hiding this comment.
@bvellanki : Can you please verify what message.getWorkflowUser() is if falcon entity is scheduled as a different user than falcon?
If it's falcon then fix you provided should be moved here so that it can handle multiple WF engines : say FalconWorkflowEngine, OozieWorkflowEngine and any other engine supported in future.
|
This error was not reproducible in multiple falcon clusters. It is only seen in a specific test cluster, hence we suspect this to be environment issue and closing the Jira. Will reopen if it can be reproduced. |
No description provided.