Cluster stuck at ‘creating’ status if creation is failed

Summary

After attempting to add a Group Level Kubernetes cluster, it got stuck and when loading the page for the cluster in GitLab just spun (see screenshot). I was then unable to remove the cluster via the UI.

Steps to reproduce

Not exactly sure, but presumabably if you create a cluster via the GKE connector and then kill the cluster build mid-flight in GKE it will cause this issue.

Example Project

https://gitlab.com/kencjohnston-apps (although I'm actively trying to clean it up and get a group-cluster working)

What is the current bug behavior?

Spins

What is the expected correct behavior?

Some ability to remove the cluster integration and it not falling into a limbo state.

Relevant logs and/or screenshots

Screen_Shot_2019-10-14_at_12.10.56_PM

Screen_Shot_2019-10-14_at_12.11.03_PM

Output of checks

(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)

Results of GitLab environment info

Expand for output related to GitLab environment info 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:env:info)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production)

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


(we will only investigate if the tests are passing)

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Edited by Thong Kuah