Issue
When attempting to export a Fusion app, the operation fails with an HTTP 500 error. The error details may include:
"type" : "RESTError",
"httpStatusCode" : 500,
"error" : "OIE-0006",
"message" : "Can't create temporary file",
"details" : "Error writing into temp file for export /tmp/exportFile<random_id>.tmp",
"httpStatusMessage" : "Internal Server Error"This typically affects a single app while other apps export successfully.
Diagnosis
To confirm the issue:
Attempt to export the app from the Fusion UI or using the API.
Check the Fusion service logs for the affected namespace. In Kubernetes, this can be done with:
kubectl logs <api-service-pod> -n <fusion-namespace>Search for messages containing:
Error reading Blobmissing partCorrupted blob
Example log entry:
Caused by: java.lang.Throwable: Corrupted blob 'prefs-<appname>._lw_tmp_<timestamp>', missing part: <UUID>_1If this pattern appears, the export failure is due to a corrupted blob file.
Environment
Fusion 5.x and above
Cause
When exporting an app, Fusion gathers various resources, including system-level configurations, preferences, and data stored in the prefs blob from the system_blobs collection. If any part of a required blob is missing or corrupted, Fusion cannot read or serialize the data fully, causing the export process to fail.
Resolution
1. Identify the corrupted blob file
Use Fusion logs to determine the blob name from the error message.
Note down the blob file that's corrupted (for example:
prefs-<appname>._lw_tmp_<timestamp>).
2. Remove the corrupted blob
Locate the blob file using the value identified from logs.
Delete the blob from the blob ui.
3. Retry the app export
After deletion, run the export operation again from the Fusion UI or via API.
Confirm that the export completes successfully and produces a valid
.zipfile.
Note: Always ensure that the blob is not part of active processing before deletion.