[oozie] External workflow with multiple kill nodes breaks workflow dashboard

Description

If submitting a workflow to oozie manually and trying to monitor its progress using HUE, the workflow dashboard is broken if multiple kill nodes are defined in the workflow.

What specifically is broken?

1. The graph visualization is incorrect and just shows boxes, no connecting arrows or details on each box (see )
2. The actions of the workflow are not shown and the message "There are no actions to be shown" is displayed (see )
3. The definition of the workflow is not a formatted read-only XML but a 2 lines, scrollable textbox with a width of maybe 30 characters. (see )

Even after workflow completion the actions are not displayed, so it is impossible to get to the actual logs of the job or debug something in case the job failed. This renders hue rather useless for this type of workflow

Why is this a bug?

According to oozie documentation this type of workflow definition is correct and thus should not lead to display issues in HUE, especially as it worked before.

A workflow definition may have zero or more kill nodes.

How to reproduce the issue?

Use this sample XML and properties file of a workflow, upload it to e.g. /tmp/test_workflow_manual and start manually by submitting it to oozie via

oozie job --oozie [oozie_host:port/oozie] -run -config job.properties

Sample job.properties

oozie.wf.application.path=hdfs://namenode_hostname:8020/tmp/test_workflow_manual
appPath=hdfs://namenode_hostname/tmp/test_workflow_manual
jobTracker=jobtracker_hostname:8032
nameNode=hdfs://namenode_hostname:8020
oozie.use.system.libpath=true

Sample workflow.xml

<workflow-app name="Test_Workflow" xmlns="uri:oozie:workflow:0.5">
    <start to="shell-e80f"/>
    <kill name="Kill">
        <message>Action failed, error message[${wf:errorMessage(wf:lastErrorNode())}]</message>
    </kill>
    <kill name="Kill2">
        <message>According to oozie spec a workflow definition may have zero or more kill nodes</message>
    </kill>
    <action name="shell-e80f">
        <shell xmlns="uri:oozie:shell-action:0.1">
            <job-tracker>${jobTracker}</job-tracker>
            <name-node>${nameNode}</name-node>
            <exec>ls -l</exec>
              <capture-output/>
        </shell>
        <ok to="End"/>
        <error to="Kill"/>
    </action>
    <end name="End"/>
</workflow-app>

Open the workflow dashboard for this workflow and check out.