[DATALAB-1226] [AWS]: Notebook stopping fails if it has active computational resources

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Done
• Fix Version/s: v.2.2
• Component/s: DataLab Main
• Labels: AWS Back-end Debian RedHat pull-request-available
• Environment: AWS
• Epic Link: DataLab Compute Engine
• Sprint: Apache DLab release 2.2
• Assignee: Oleg Fuks
• Reporter: Vira Vitanska
• Created: 31/Oct/19 14:36
• Updated: 18/Nov/19 17:17
• Resolved: 18/Nov/19 17:17

Description

Preconditions:

1. EMR is in running status
2. Spark cluster is in running status

Steps to reproduce:

1. Go to 'resources_list' page
2. Click action menu for notebook
3. Choose 'Stop' notebook

Actual result:

1. EMR is in terminated status on Dlab UI
2. EMR is in running status on AWS console
3. Spark cluster is in failed status on Dlab UI
4. Spark cluster is in running status on AWS console
5. Notebook is in failed status on Dlab UI
6. Notebook is in running status on AWS console

Expected result:

1. EMR is in terminated status on Dlab UI
2. EMR is in terminated status on AWS console
3. Spark cluster is in stopped status on Dlab UI
4. Spark cluster is in stopped status on AWS console
5. Notebook is in stopped status on Dlab UI
6. Notebook is in stopped status on AWS console

Issue Links

• links to: GitHub Pull Request #375