Bulk Status Report Export feature Writing in \tmp file during export

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

Bulk Status Report Export while exporting the status report it’s copying shell and node scripts in a /tmp location, It’s trying to execute the script in /tmp. Since the write permission is restricted the 'node' file in playwright-java-xxx folder created in /tmp is failing with permissions denied. 

 

Steps to Reproduce: 

1. Login to clarity and navigate to Status report workspace 
2. Export the status report 
3. Login to server where clarity is running and observe /tmp folder 

Expected Results: During export nothing should be written in the /tmp folder and still Bulk Status Report Export functionality should work 

Actual Results: During Bulk Status Report Export files are being written in the /tmp folder and since write permission is not provided in /tmp location the Bulk Status Report Export fails to export. 

Environment

Release : 16.1.x

Cause

The current functionality of Bulk Status Report Export invokes chrome and its chrome default behavior is to write in /tmp location and once the export is complete the written files are automatically deleted. 

This is not a defect however since multiple customer dont tend to give write permission to /tmp folder, Broadcom has decided to look into redesigning the same and not writing to /tmp location 

Resolution

The resolution to this issue is included in 16.1.3. This was originally tracked as DE69182.

Workaround till the behavior is changed

• Provide write permission to /tmp location to the user used for running clarity services