[ 
https://issues.apache.org/jira/browse/DATALAB-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477034#comment-17477034
 ] 

Denys Yankiv commented on DATALAB-1891:
---------------------------------------

Issue is hard to reproduce.  Main problem causing this is expiration of refresh 
token and error response from Keycloak server. Further investigation will 
require more time and resources. For this reason ticket is postponed.

> Web terminal is not always opened successfully
> ----------------------------------------------
>
>                 Key: DATALAB-1891
>                 URL: https://issues.apache.org/jira/browse/DATALAB-1891
>             Project: Apache DataLab
>          Issue Type: Bug
>          Components: DataLab Main
>    Affects Versions: v.2.5.1, v.2.5.2
>            Reporter: Vira Vitanska
>            Assignee: Denys Yankiv
>            Priority: Minor
>              Labels: AWS, Debian, Known_issues(release2.5.1), RedHat
>             Fix For: v.2.5.2
>
>         Attachments: Web terminal - it is reproduced.png, Web terminal 
> 29-07-2020.txt, Web terminal.png, image-2020-10-07-15-44-39-199.png
>
>
> This bug was found on AWS from branch epm-v2.3.0  (It has not been checked on 
> Azure/GCP). This bug was found on GCP as well, in some minutes (after login) 
> terminal could not be opened successful ( branch-2.4.0). If user opens 
> terminal right away after login the terminal opens successfully.
> *Preconditions:*
> 1. Notebook is created from branch epm-v2.3.0
> *Steps to reproduce:*
> 1. Open Web terminal
> *Actual result:*
>  # Web terminal is not always opened successfully
> *Expected result:*
>  # Web terminal is always opened successfully
> ----
> This bug was reproduced 29/07/2020 on AWS
> This bug was reproduced 07/10/2020 on AWS from develop branch



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

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

Reply via email to