You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@dlab.apache.org by "Vira Vitanska (Jira)" <ji...@apache.org> on 2020/03/20 10:35:00 UTC
[jira] [Updated] (DLAB-1639) Investigate why notebook
template/computational resource are not always available after provisioning
starting
[ https://issues.apache.org/jira/browse/DLAB-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vira Vitanska updated DLAB-1639:
--------------------------------
Summary: Investigate why notebook template/computational resource are not always available after provisioning starting (was: Investigate why notebook template/computational resource are not alway available after provisioning starting)
> Investigate why notebook template/computational resource are not always available after provisioning starting
> -------------------------------------------------------------------------------------------------------------
>
> Key: DLAB-1639
> URL: https://issues.apache.org/jira/browse/DLAB-1639
> Project: Apache DLab
> Issue Type: Task
> Components: DLab Main
> Reporter: Vira Vitanska
> Assignee: Oleg Fuks
> Priority: Major
> Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat
> Fix For: v.2.3
>
>
> Edge node is created on remote AWS endpoint. After restarting provisioning not always notebook and computational resources are available. Please, investigate it and fix it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@dlab.apache.org
For additional commands, e-mail: dev-help@dlab.apache.org