[DATALAB-2014] [GCP]: Investigate why VPC remains after SSN termination

• Type: Task
• Status: Closed
• Priority: Minor
• Resolution: Done
• Fix Version/s: v.2.4
• Component/s: DataLab Main
• Labels: Debian DevOps GCP
• Epic Link: Investigation
• Sprint: Apache DLab release 2.4
• Assignee: Leonid Frolov
• Reporter: Vira Vitanska
• Created: 01/Sep/20 07:26
• Updated: 16/Sep/20 08:45
• Resolved: 15/Sep/20 11:09

Description

If VPCs remain and collect it is impossible to create SSN due to maximum VPC name reaching.

Investigate why VPC remains after SSN termination

---

Case when maximum VPC name is reached

Step to reproduce:

1. Create SSN via Jenkins job

Actual result:

1. SSN creatin fails: 'VPC vi-gcp-0109-vpc has been created
   Traceback (most recent call last):
   File "/root/scripts/ssn_prepare.py", line 115, in <module>
   ssn_conf['vpc_selflink'] = GCPMeta.get_vpc(ssn_conf['vpc_name'])['selfLink']'

Expected result:

1. SSN creation is successful