[ 
https://issues.apache.org/jira/browse/DLAB-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vira Vitanska updated DLAB-334:
-------------------------------
    Description: 
*Preconditions:*
1. EMR or Spark standalone cluster is created

*Steps to reproduce:*
1. terminate EMR or Spark standalone cluster

*Actual result:*
1. EMR/Saprk standalone termination fails on DLab UI
2. EMR/Saprk is terminated on AWS console

!EMR termination.PNG!

!AWS console.PNG!

 

*Expected result:*
1. EMR/Saprk standalone termination is successful on DLab UI
2. EMR/Saprk is terminated on AWS console

***Why command is done for jupyter s*udo: rm -rf 
/home/dlab-user/.local/share/jupyter/kernels/*_vit_2112-vira_vitanska-des-rs-519spo-cust-5ca34*?

Also the bug was reproduced if stop RStudio with related clusters (GCP)

  was:
*Preconditions:*
1. EMR or Spark standalone cluster is created

*Steps to reproduce:*
1. terminate EMR or Spark standalone cluster

*Actual result:*
1. EMR/Saprk standalone termination fails on DLab UI
2. EMR/Saprk is terminated on AWS console

!EMR termination.PNG!

!AWS console.PNG!

 

*Expected result:*
1. EMR/Saprk standalone termination is successful on DLab UI
2. EMR/Saprk is terminated on AWS console

***Why command is done for jupyter s*udo: rm -rf 
/home/dlab-user/.local/share/jupyter/kernels/*_vit_2112-vira_vitanska-des-rs-519spo-cust-5ca34*?


> [AWS][GCP][RStudio]: Sometimes cluster termination fails
> --------------------------------------------------------
>
>                 Key: DLAB-334
>                 URL: https://issues.apache.org/jira/browse/DLAB-334
>             Project: Apache DLab
>          Issue Type: Bug
>          Components: AWS, GCP
>         Environment: AWS, GCP
> RStudio
>            Reporter: Vira Vitanska
>            Assignee: Demyan Mysakovets
>            Priority: Minor
>              Labels: Debian, DevOps, GCP_demo, RedHat
>             Fix For: v.2.1, v.2.2
>
>         Attachments: AWS console.PNG, EMR termination.PNG
>
>
> *Preconditions:*
> 1. EMR or Spark standalone cluster is created
> *Steps to reproduce:*
> 1. terminate EMR or Spark standalone cluster
> *Actual result:*
> 1. EMR/Saprk standalone termination fails on DLab UI
> 2. EMR/Saprk is terminated on AWS console
> !EMR termination.PNG!
> !AWS console.PNG!
>  
> *Expected result:*
> 1. EMR/Saprk standalone termination is successful on DLab UI
> 2. EMR/Saprk is terminated on AWS console
> ***Why command is done for jupyter s*udo: rm -rf 
> /home/dlab-user/.local/share/jupyter/kernels/*_vit_2112-vira_vitanska-des-rs-519spo-cust-5ca34*?
> Also the bug was reproduced if stop RStudio with related clusters (GCP)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org

Reply via email to