[
https://issues.apache.org/jira/browse/DLAB-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bohdan Hliva updated DLAB-1075:
-------------------------------
Summary: Stop project simultaneously should affect related instances (was:
Stopa project simultaneously should affect related instances)
> Stop project simultaneously should affect related instances
> -----------------------------------------------------------
>
> Key: DLAB-1075
> URL: https://issues.apache.org/jira/browse/DLAB-1075
> Project: Apache DLab
> Issue Type: Bug
> Components: DLab Main
> Reporter: Vira Vitanska
> Assignee: Bohdan Hliva
> Priority: Major
> Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat
> Fix For: v.2.2
>
>
> *Preconditions:*
> Environment is created
> Steps to reproduce:
> # Go to 'Manage environment' popup
> # Click stop project
> *Actual result:*
> # Only alone project is stopped
> # Related instances are in running status
> *Expected result*
> # Project is stopped
> # Related instances are stopped
> *Notes:*
> * Stop project should take into consideration instances in
> 'creating/configuring/terminating/stopping/starting' statuses. If any
> instance is in these statuses do not allowed admin to stop/terminate project
> * If project is already terminated convey an information massage to admin if
> admin hovers a mouse on stop/terminate icon: 'The environment is not active'
> * If at least one instance is in running status and project is stopped and
> the other instances as well - allow admin to stop project
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
