[ 
https://issues.apache.org/jira/browse/DATALAB-2381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vira Vitanska updated DATALAB-2381:
-----------------------------------
    Summary: [Configuration page]: Instance status is not distinguished by 
endpoint  (was: [Configuration page]:)

> [Configuration page]: Instance status is not distinguished by endpoint
> ----------------------------------------------------------------------
>
>                 Key: DATALAB-2381
>                 URL: https://issues.apache.org/jira/browse/DATALAB-2381
>             Project: Apache DataLab
>          Issue Type: Bug
>      Security Level: Public(Regular Issues) 
>          Components: DataLab Main
>            Reporter: Vira Vitanska
>            Assignee: Yurii Tykhun
>            Priority: Major
>              Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat
>             Fix For: v.2.5
>
>
> *Preconditions:*
>  # Project1 has edge1 (internal endpoint) and edge2 (external endpoint)
>  # In local endpoint one of the resource in in creating/terminating status
>  # User is located in Configuration page
> *Steps to reproduce:*
>  # Choose external endpoint in dropdown list Selected endpoint
>  # Check off Provisioning
>  # Click on Restart button
>  # Submit restart
> *Actual result:*
>  # Restart is not done
>  # Information message appears:
> {code:java}
> Provisioning service: can not be restarted because one of resources is in 
> processing stage. Please try again later.{code}
> *Expected result:*
>  # Restart is done
> (i) Resources which are in processing stage should be distinguished by 
> endpoints. Admin should be able to restart provisioning service for 
> endpoint1(there aren't any resources which are in processing stage) even if 
> for endpoint2 some resources are in processing stage.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to