IssueTracker

Thank you for reporting this issue. I was able to reproduce the issue and have forwarded this report to our engineering team. Any progress updates and a resolution will be posted on this thread.

team what is the latest on this ?, we can still produce this bug!!!

Team what it the status of this on You, Please we still facing this bug every time, Please hurry up, what i know that GCP team is not lazy

I just looked into the internal issue and saw that version 190.0.0 of Cloud SDK was expected to fix this bug. Please run $ gcloud components update,  and try again. If you are still experiencing the issue, please post the full stack trace using --verbosity=debug and the output of running $ gcloud info.

This issue is not fixed in 211.0.0. Neither command is executed with an appropriate '-d' flag (at least for my use case). The default for psql is to utilize the username as the database name, which is why I'm getting this error. I've replaced some sensitive data with placeholders.

GA command:

$ gcloud --verbosity=debug sql connect psqlInstance1 --user=bobuser
DEBUG: Running [gcloud.sql.connect] with arguments: [--user: "bobuser", --verbosity: "debug", INSTANCE: "psqlInstance1"]
Whitelisting your IP for incoming connection for 5 minutes...done.
Connecting to database with SQL user [bobuser].DEBUG: Executing command: [u'psql', u'-h', u'192.168.1.1', u'-U', u'bobuser', u'-W']
Password for user bobuser:
psql: FATAL:  database "bobuser" does not exist


Beta command:

$ gcloud --verbosity=debug beta sql connect psqlInstance1 --user=bobuser
DEBUG: Running [gcloud.beta.sql.connect] with arguments: [--user: "bobuser", --verbosity: "debug", INSTANCE: "psqlInstance1"]
Whitelisting your IP for incoming connection for 5 minutes...done.
Connecting to database with SQL user [bobuser].DEBUG: Executing command: [u'psql', u'-h', u'192.168.1.1', u'-U', u'bobuser', u'-W']
Password for user bobuser:
psql: FATAL:  database "bobuser" does not exist


Gcloud info:

$ gcloud info
Google Cloud SDK [211.0.0]

Platform: [Linux, x86_64] ('Linux', 'cs-6000-devshell-vm-d853b350-fed4-4d5d-7f29-daede39fc0ba', '4.14.33+', '#1 SMP Sun Aug 5 10:53:14 PDT 2018', 'x86_64', '')
Python Version: [2.7.13 (default, Nov 24 2017, 17:33:09)  [GCC 6.3.0 20170516]]
Python Location: [/usr/bin/python2]
Site Packages: [Disabled]

Installation Root: [/google/google-cloud-sdk]
Installed Components:
  datalab: [20180503]
  kubectl: []
  container-builder-local: []
  pubsub-emulator: [2018.02.02]
  core: [2018.08.03]
  app-engine-java: [1.9.64]
  app-engine-python: [1.9.73]
  app-engine-php: [ ]
  docker-credential-gcr: []
  app-engine-python-extras: [1.9.69]
  beta: [2018.07.16]
  gsutil: [4.33]
  cloud-datastore-emulator: [2.0.1]
  cbt: []
  alpha: [2018.08.03]
  gcd-emulator: [v1beta3-1.0.0]
  app-engine-go: []
  bq: [2.0.34]
System PATH: [/home/bobuser/bin:/home/bobuser/gopath/bin:/google/gopath/bin:/google/google-cloud-sdk/bin:/usr/local/go/bin:/opt/gradle/bin:/opt/maven/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/nvm/versions/node/v8.9.4/bin:/google/go_appengine:/google/google_appengine]
Python PATH: [/google/google-cloud-sdk/lib/third_party:/google/google-cloud-sdk/lib:/usr/lib/python2.7:/usr/lib/python2.7/plat-x86_64-linux-gnu:/usr/lib/python2.7/lib-tk:/usr/lib/python2.7/lib-old:/usr/lib/python2.7/lib-dynload]
Cloud SDK on PATH: [True]
Kubectl on PATH: [/google/google-cloud-sdk/bin/kubectl]

WARNING: There are old versions of the Google Cloud Platform tools on your system PATH.
  /google/go_appengine/dev_appserver.py
  /google/go_appengine/endpointscfg.py

Installation Properties: [/google/google-cloud-sdk/properties]
User Config Directory: [/tmp/tmp.GASefIHPnC]
Active Configuration Name: [cloudshell-11324]
Active Configuration Path: [/tmp/tmp.GASefIHPnC/configurations/config_cloudshell-11324]

Account: [bobuser@domain.com]
Project: [bob-project]

Current Properties:
  [metrics]
    environment: [devshell]
  [core]
    project: [bob-project]
    account: [bobuser@domain.com]
    disable_usage_reporting: [False]
  [component_manager]
    disable_update_check: [True]
  [compute]
    gce_metadata_read_timeout_sec: [5]

Logs Directory: [/tmp/tmp.GASefIHPnC/logs]
Last Log File: [/tmp/tmp.GASefIHPnC/logs/2018.08.13/15.37.11.775017.log]

git: [git version 2.11.0]
ssh: [OpenSSH_7.4p1 Debian-10+deb9u3, OpenSSL 1.0.2l  25 May 2017]

To clarify, version 190.0.0 added a --database flag to the beta command, as requested in the original post. You would need to run

$ gcloud --verbosity=debug sql connect psqlInstance1 --user=bobuser --database=$MY_DATABASE

This is not yet available in the GA command.

Thank you for clarifying. The beta command does include the --database flag, and solves this issue.

$ gcloud beta sql connect ${instance_name} --user=${user_name} --database=${database_name}

Great! Glad the issue is fixed for you.

Hi

this works for us, except in one case:

- one developer uses Cloud Shell and he has restricted IAM rights.
- when he uses gcloud beta sql connect with --database= option, he gets an error (see screenshot)

Thanks !

Still does not work for me in Sweden.  Fails when using regular gcloud and gcloud beta aswell =(

Does not work. I get the same proxy error as mentioned above.

Fails here too! Best regards from Oslo.

Hi,
Could you provide a quick correction to this issue? My instance is in europe-west1-b.
Regards

This needs to be out of beta and into production ASAP, or at the very least mentioned in the gcloud sql connect docs. sql connect is completely useless without this; and its wasted hours of my time to get to this page.

I am having this issue today:
Even when specifying the database, it tries to connect to the database with the user name

Is there any further configuration to enable this command?

This is still happening. I tried in Cloud Shell with the proposed workarounds, but I got the same problem described 2 years ago in the first comment.

If this can not be fixed, maybe makes sense to update the documentation of "gcloud sql connect" accordingly:
https://cloud.google.com/sdk/gcloud/reference/sql/connect

This is still happening. I tried in Cloud Shell with the proposed workarounds, but I got the same problem described 2 years ago in the first comment.

If this can not be fixed, maybe makes sense to update the documentation of "gcloud sql connect" accordingly:
https://cloud.google.com/sdk/gcloud/reference/sql/connect

This is still happening for us as well.

I have created a postgres database with the name: 'backend' and a user "appengine". When specifying the database:

❯ gcloud sql connect <instance name> --user=appengine --database=backend
Allowlisting your IP for incoming connection for 5 minutes...done.
Connecting to database with SQL user [appengine].Password:
psql: error: FATAL:  database "appengine" does not exist


I've had to specify the database using a postgres environment variable:

❯ PGDATABASE=backend gcloud sql connect <instance name>--user=appengine