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

Vira Vitanska updated DLAB-1687:
--------------------------------
    Description: 
*Preconditions:*

1. Notebook is created by user1
1. Spark cluster is created on notebook

*Steps to reproduce:*
 # Login DLab by user2
 # Go to environment management page
 # Stop Notebook of user1

*Actual result:*
 # Notebook stopping is forbidden

*Expected result:*
 # Notebook stopping is allowed
-----
The same bug is when we terminate notebook.

 

 

  was:
*Preconditions:*

1. Notebook is created by user1

*Steps to reproduce:*
 # Login DLab by user2
 # Go to environment management page
 # Stop Notebook of user1

*Actual result:*
 # Notebook stopping is forbidden

*Expected result:*
 # Notebook stopping is allowed
-----
The same bug is when we terminate notebook.

 

 


> [Branch-1571]: Notebook management of the other user is forbidden for admin
> ---------------------------------------------------------------------------
>
>                 Key: DLAB-1687
>                 URL: https://issues.apache.org/jira/browse/DLAB-1687
>             Project: Apache DLab
>          Issue Type: Bug
>          Components: DLab Main
>            Reporter: Vira Vitanska
>            Assignee: Oleg Fuks
>            Priority: Major
>              Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat
>             Fix For: v.2.3
>
>         Attachments: Notebook.png
>
>
> *Preconditions:*
> 1. Notebook is created by user1
> 1. Spark cluster is created on notebook
> *Steps to reproduce:*
>  # Login DLab by user2
>  # Go to environment management page
>  # Stop Notebook of user1
> *Actual result:*
>  # Notebook stopping is forbidden
> *Expected result:*
>  # Notebook stopping is allowed
> -----
> The same bug is when we terminate notebook.
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to