gcloud irregular file-permissions failure

[Joshua Fox]

In my Jenkins runs, gcloud randomly generates permissions errors as below. I verified that successful and failed runs are on the same machine, with the same user, in the same directory.

(I think the command causing failure is gcloud auth activate-service-account --key-file=fuf-automation-server.json  )

(In success conditions we get  "gcloud credential helpers already registered correctly")

Has anyone seen similar issues? Under what conditions can such failure occur? Can I redefine the logging and configuration directory to avoid this?

  

---------------------------------------

Failure logs:

 

 

WARNING: Could not setup log file in /.config/gcloud/logs, (Error: Could not create directory [/.config/gcloud/logs/2018.12.13]: Permission denied.

Please verify that you have permissions to write to the parent directory.)

The following settings will be added to your Docker config file 

located at [/.docker/config.json]:

 {

  "credHelpers": {

    "gcr.io": "gcloud", 

    "us.gcr.io": "gcloud", 

    "eu.gcr.io": "gcloud", 

    "asia.gcr.io": "gcloud", 

    "staging-k8s.gcr.io": "gcloud", 

    "marketplace.gcr.io": "gcloud"

  }

}

Do you want to continue (Y/n)?  

ERROR: (gcloud.auth.configure-docker) Error writing Docker configuration to disk: [Errno 2] No such file or directory: '/.docker/tmpzki75K'

WARNING: Could not setup log file in /.config/gcloud/logs, (Error: Could not create directory [/.config/gcloud/logs/2018.12.13]: Permission denied.

Please verify that you have permissions to write to the parent directory.)

ERROR: (gcloud.auth.activate-service-account) Could not create directory [/.config/gcloud]: Permission denied.

Please verify that you have permissions to write to the parent directory.

$ docker rm -f 06aa3ee44b9f03e75eaaa98fda1c4ff6f771a3b84d9ea416a39c8f6637599ccc

WARNING: Could not setup log file in /.config/gcloud/logs, (Error: Could not create directory [/.config/gcloud/logs/2018.12.13]: Permission denied.

Please verify that you have permissions to write to the parent directory.)

ERROR: (gcloud.config.set) Failed to create the default configuration. Ensure your have the correct permissions on: [/.config/gcloud/configurations].

  Could not create directory [/.config/gcloud/configurations]: Permission denied.

Please verify that you have permissions to write to the parent directory.

WARNING: Could not setup log file in /.config/gcloud/logs, (Error: Could not create directory [/.config/gcloud/logs/2018.12.13]: Permission denied.

Please verify that you have permissions to write to the parent directory.)

ERROR: (gcloud.config.set) Failed to create the default configuration. Ensure your have the correct permissions on: [/.config/gcloud/configurations].

  Could not create directory [/.config/gcloud/configurations]: Permission denied.

Please verify that you have permissions to write to the parent directory.

WARNING: Could not setup log file in /.config/gcloud/logs, (Error: Could not create directory [/.config/gcloud/logs/2018.12.13]: Permission denied.

Please verify that you have permissions to write to the parent directory.)

ERROR: (gcloud.config.set) Failed to create the default configuration. Ensure your have the correct permissions on: [/.config/gcloud/configurations].

  Could not create directory [/.config/gcloud/configurations]: Permission denied.

Please verify that you have permissions to write to the parent directory.

 

[Nicolas (Google Cloud Platform Support)]

Hello Joshua,

This could be caused by your disk running out of space and the system is sending you a generic “permission denied” error.

If you are using Google Cloud Shell  try to restore it to a clean state by following the following steps:

1. Open your Cloud Shell.

2. In the Cloud Shell menu, click the "Open in new window icon" (next to the Close icon) to open the cloud shell on a new and separate tab.

3. Append to the URL of this new window the parameter cloudshellsafemode=true. The URL should look something like this [1].

4. The previous step will restart your Cloud Shell in safe mode and log you in as root (This might take a couple of minutes).

5. Once your Cloud Shell has restarted you’ll have to remove all files from your home directory by executing the command [2]. (If you want to check if there are personal files on your home directory you can do so by executing [3]).

6. Once the home directory is cleaned, proceed to restart your Cloud Shell. Click the three dotted line icon, and then click on Restart. 

7. On the confirmation dialog displayed, select “Want a clean VM state” and then click Restart Cloud Shell.

To better assist you, it would be helpful if you could provide extra log information. To do so I recommend changing the default verbosity to the debug level by running the same command but adding the --verbosity=VERBOSITY; default="debug" flag[1].

As your issue seems to be a specific technical issue you would have better assistance from the community by posting in StackOverflow as Google Groups is intended for general discussion. You should post to StackOverflow with the extra log information to have the developer community assist you.

[1] https://cloud.google.com/sdk/gcloud/reference/#--verbosity

[2] https://issuetracker.google.com/issues/new?component=187143&template=0