Cannot create GKE cluster bc can't verify billing

Summary

Unable to create cluster because unable to verify billing enabled for project. Billing is enabled and I do believe I am logged in with the appropriate account.

Steps to reproduce

Install ee Omnibus on Ubuntu 16.04 xenial VM in GCP and follow the steps to configure Google OAuth2 OmniAuth Provider for the Omnibus install (https://gitlab.com/help/integration/google). Create a project and go to add a cluster. Gitlab finds the projects in the dropdown. When I select the target project that does have billing enabled it says that it cannot verify that it does.

Example Project

This is occurs on the EE version built not on gitlab.com

What is the current bug behavior?

When I go to select my Google Cloud Platform project, Validation message pops up in the 'Enter the details for your k8s cluster' form, stating 'We could not verify that one of your projects on GCP has billing enabled. Please try again.' preventing me from moving forward with the cluster creation. Same thing happens when I try to go add an existing cluster.

What is the expected correct behavior?

I should be able to move to the next step when I select my project that has billing enabled, so that I can create a kubernetes cluster on the GCP/GKE.

Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.)

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)

System information
System:         Ubuntu 16.04
Proxy:          no
Current User:   git
Using RVM:      no
Ruby Version:   2.6.3p62
Gem Version:    2.7.9
Bundler Version:1.17.3
Rake Version:   12.3.2
Redis Version:  3.2.12
Git Version:    2.21.0
Sidekiq Version:5.2.7
Go Version:     unknown
GitLab information
Version:        12.0.0-ee
Revision:       3b13818e833
Directory:      /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:     PostgreSQL
DB Version:     10.7
URL:            https://gitlab.REDACTED.com
HTTP Clone URL: https://gitlab.REDACTED.com/some-group/some-project.git
SSH Clone URL:  git@gitlab.REDACTED.com:some-group/some-project.git
Elasticsearch:  no
Geo:            no
Using LDAP:     no
Using Omniauth: yes
Omniauth Providers: google_oauth2
GitLab Shell
Version:        9.3.0
Repository storage paths:
- default:      /var/opt/gitlab/git-data/repositories
GitLab Shell path:              /opt/gitlab/embedded/service/gitlab-shell
Git:            /opt/gitlab/embedded/bin/git


Worth noting that I redacted my URL, HTTP Clone URL, and SSH Clone URL top level domain name from the log pasted above to prevent needlessly sharing it. Let me know if I can provide more details in a secure way.
(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)

Incoming Email: ... Reply by email is disabled in config/gitlab.yml
Checking Incoming Email ... Finished
Checking LDAP ...
LDAP: ... LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab App ...
Git configured correctly? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... yes
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory exists? ... yes
Uploads directory has correct permissions? ... yes
Uploads directory tmp has correct permissions? ... skipped (no tmp uploads folder yet)
Init script exists? ... skipped (omnibus-gitlab has no init script)
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
Projects have namespace: ... 
2/1 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.5.3 ? ... yes (2.6.3)
Git version >= 2.21.0 ? ... yes (2.21.0)
Git user has default SSH configuration? ... yes
Active users: ... 2
Elasticsearch version 5.6 - 6.x? ... skipped (elasticsearch is disabled)
Checking GitLab App ... Finished
Checking GitLab subtasks ... Finished


(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)