[AO-1] ONAP Installation fails when trying to read the /opt/scripts/temp file Created: 18/Apr/19  Updated: 04/Jun/19  Due: 23/Apr/19

Status: To Do
Project: Addon ONAP
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Medium
Reporter: Roddric Boswell Assignee: David Plunkett
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File parameters.env     Text File scriptexecutor.log    

 Description   

When the OANP installation starts it fails with the following error message:

2019-04-18 19:29:46.197 DEBUG 65053 — [SimpleAsyncTaskExecutor-11] a.b.s.i.RemoteScriptExecutionServiceImpl : + cat /opt/scripts/temp
2019-04-18 19:29:46.198 DEBUG 65053 — [SimpleAsyncTaskExecutor-11] a.b.s.i.RemoteScriptExecutionServiceImpl : cat: /opt/scripts/temp: No such file or directory
2019-04-18 19:29:46.198 DEBUG 65053 — [SimpleAsyncTaskExecutor-11] a.b.s.i.RemoteScriptExecutionServiceImpl : Script exit code :1
2019-04-18 19:29:46.199 ERROR 65053 — [SimpleAsyncTaskExecutor-11] org.camunda.bpm.engine.context : ENGINE-16006 BPMN Stack Trace:
Task_19usii1 (activity-execute, ProcessInstance[2196])
Task_19usii1, name=ScriptExecutorTask
^

Task_1ahdja4, name=ScriptExecutorTask
^

StartEvent_1, name=ScriptExecutionStartingPoint

2019-04-18 19:29:46.199 ERROR 65053 — [SimpleAsyncTaskExecutor-11] org.camunda.bpm.engine.context : ENGINE-16004 Exception while closing command context: Problem while executing scriptproblem while executing the script. exit code :1

 

I will be attaching the scriptexecutor.log file and the parameters.env file to this ticket.

 



 Comments   
Comment by David Plunkett [ 04/Jun/19 ]

Updates in Akraino R1 should allow ONAP to deploy to a Rover site.  Work is still ongoing to enable on Unicycle.  There is also work on updating to ONAP Casablanca release.  I expect a minor release before the end of summer will address the remaining open issues.

Generated at Sat Feb 10 05:52:01 UTC 2024 using Jira 9.4.5#940005-sha1:e3094934eac4fd8653cf39da58f39364fb9cc7c1.