[
https://issues.apache.org/jira/browse/DLAB-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16792819#comment-16792819
]
Anna Orlovska edited comment on DLAB-390 at 3/14/19 4:29 PM:
-------------------------------------------------------------
This problem is reproduced on environment v2.1-RC2 for next notebooks: Jupyter,
Zeppelin, RStudio. TensorFlow has not such defect.
was (Author: orlann):
This problem is reproduced on environment v2.1-RC2 for all notebooks.
> [GCP]: Notebook starting fails (previously it was stopped)
> ----------------------------------------------------------
>
> Key: DLAB-390
> URL: https://issues.apache.org/jira/browse/DLAB-390
> Project: Apache DLab
> Issue Type: Bug
> Components: GCP
> Environment: GCP
> Reporter: Vira Vitanska
> Assignee: Demyan Mysakovets
> Priority: Blocker
> Labels: Debian, DevOps, GCP_demo
> Fix For: v.2.2
>
> Attachments: Notebook UI.PNG, RStudio starting.PNG, jup-error.png
>
>
> First of all the bug was found during starting RStudio. And now the bug
> reproduced for Jupyter, Zeppelin randomly. Notebook after starting fails or
> if starting is successful it is impossible to go to UI Notebook
> *Preconditions:*
> RStudio is in 'stopped' status
> *Steps to reproduce:*
> 1. Start RStudio
> *Actual result:*
> RStudio starting fails with error
> *fabric.exceptions.NetworkError: Timed out trying to connect to 172.31.16.14
> (tried 100 times)*
> !RStudio starting.PNG!
> *Expected result:*
> RStudio starting is successful
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
