Investigate: Permission denied: u'/var/run/elyra/runtime/kernel-xxxxx.json about enterprise_gateway HOT 3 CLOSED

This might be related to having the kernel initialization fail, and elyra/yarn then retrying

from enterprise_gateway.

Yes, this is during the startup of a persisted session that had used the local server (loopback) in pull or socket mode.
One approach would be to set the appropriate values so the write is skipped since it isn't necessary. Another is to use groups to get around permissions. Or we need to have launchers write to a different location, then elyra move/rename the file, but this is ONLY necessary in loopback.

from enterprise_gateway.

This issue can be resolved by not calling write_connection_file() when loading from persisted sessions. There is no reason to write the connection file since its only used to initially start kernels and, in this case, the kernel is already running. So only loading the connection information (from the persisted session record) is all that required.

PR will be submitted.

from enterprise_gateway.