Oracle ZFS Storage Appliance: Workflows Fail to Execute with a (code EAKSH_SHELL

Asset ID:	1-72-1957486.1
Update Date:	2015-03-08
Keywords:

Solution Type Problem Resolution Sure

Solution 1957486.1 : Oracle ZFS Storage Appliance: Workflows Fail to Execute with a (code EAKSH_SHELL_FAILED) Failure

Applies to:

Sun Storage 7210 Unified Storage System - Version All Versions and later
Sun Storage 7410 Unified Storage System - Version All Versions and later
Sun Storage 7310 Unified Storage System - Version All Versions and later
Oracle ZFS Storage ZS3-2 - Version All Versions and later
Oracle ZFS Storage ZS3-4 - Version All Versions and later
7000 Appliance OS (Fishworks)

Symptoms

A custom workflow has been provided to assist with an issue on an Oracle ZFS Storage Appliance. The workflow is successfully uploaded to the appliance from the Maintenance Workflows interface of the BUI. It shows up in the run time list of available workflows to execute.

When the workflow is selected, it fails to execute and creates the following dialog box.

The workflow failed to execute. Workflow output:

aksh: uncaught error exception (code EAKSH_SHELL_FAILED) in script:
failed to execute "echo -e 'line-from-workflow\nwrite\ndisplay\nq\nq\nq\n '> /tmp/cmd.txt ":
error: Unauthorized action

This is due to an unexpected or otherwise unhandled error in the workflow; the
failure should be understood, and the workflow may need to be modified to more
gracefully handle the error by explicitly failing.
(See the workflow documentation for details.)

Cause

The user who is executing the workflow does not have privileges to execute the program.

Solution

In this particular case, the workflow executed a command (format) which is only allowed by root. Once the workflow reaches this point in the script, it will fail. You need to logout and log back in as root to run the workflow.

Creating an authorization for the user to execute workflows, will NOT solve this problem. Authorizations make no provision for the user to run the workflow as root. Seeing as most workflows require root privileges, they should always be run as root.

Attachments

This solution has no attachment