You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@datalab.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/03/04 08:26:00 UTC
[jira] [Updated] (DATALAB-1673) Instance status is not changed
after provserv starting
[ https://issues.apache.org/jira/browse/DATALAB-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated DATALAB-1673:
------------------------------------
Labels: AWS AZURE Back-end Debian GCP Known_issues(release2.3) Known_issues(release2.4) RedHat pull-request-available (was: AWS AZURE Back-end Debian GCP Known_issues(release2.3) Known_issues(release2.4) RedHat)
> Instance status is not changed after provserv starting
> ------------------------------------------------------
>
> Key: DATALAB-1673
> URL: https://issues.apache.org/jira/browse/DATALAB-1673
> Project: Apache DataLab
> Issue Type: Bug
> Components: DataLab Main
> Affects Versions: v.2.5
> Reporter: Vira Vitanska
> Assignee: Yurii Kinash
> Priority: Minor
> Labels: AWS, AZURE, Back-end, Debian, GCP, Known_issues(release2.3), Known_issues(release2.4), RedHat, pull-request-available
> Fix For: v.2.5
>
>
> *Preconditions:*
> 1. Notebook is in terminating status
> *Steps reproduce:*
> 1. Run command 'sudo supervisorctl restart all'
> *Actual result:*
> 1. Docker for notebook termination runs wit '0'
> 2. Notebook is still in terminating status on Dlab UI
> 3. Notebook is terminated on Cloud console
> *Expected result:*
> 1. Docker for notebook termination runs wit '0'
> 2. Notebook is in terminated status on Dlab UI
> 3. Notebook is terminated on Cloud console
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@datalab.apache.org
For additional commands, e-mail: dev-help@datalab.apache.org