[DATALAB-1865] [Branch-515][Azure][Jupyter]: Connection to kernel R/Scala is not successful

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Done
• Fix Version/s: v.2.5.1
• Component/s: DataLab Main
• Labels: AWS Azure Debian DevOps GCP pull-request-available
• Environment: Branch-515
• Epic Link: Update software
• Sprint: Apache DataLab release 2.5.1
• Assignee: Oleh Mykolaishyn
• Reporter: Vira Vitanska
• Created: 10/Jun/20 10:53
• Updated: 03/Nov/21 11:52
• Resolved: 03/Nov/21 11:52

Description

Preconditions:

1. Jupyter is created

Steps to reproduce:

1. Run playbook via kernel R (Local SparkR (R-3.4.4, Spark-2.4.4) and remote EMR5.28 SparkR (R-3.4.1, Spark-2.4.4))
2. Run playbook via kernel Scala (Local Apache Toree - Scala (Scala-2.11.12, Spark-2.4.4) and remote EMR 5.28 Apache Toree - Scala (Scala-2.11.12, Spark-2.4.4) )

Actual result:

1. Connection to kernel R died
2. Connection to Scala stuck

Expected result:

1. Connection to kernel R is successful

2. Connection to Scala is successful

For Azure

R/Scala

R (local)	error with connection to kernel
R (Spark)	Blocked
Scala (Local)	error with connection to kernel
Scala (Spark)	Blocked

Issue Links

• relates to: DATALAB-1812 [Branch-515][AWS][GCP][Jupyter]: Connection to kernel R/Sala is not successful
• links to: GitHub Pull Request #1298