Skip to content

Commit

Permalink
Update troubleshooting guide (#2705)
Browse files Browse the repository at this point in the history
* Update troubleshooting guide

Append information to solve permission issues by specifying appropriate VM scope.

* Update docs/troubleshooting.md

Co-authored-by: Ashmeen Kaur <57195160+ashmeenkaur@users.noreply.github.com>

---------

Co-authored-by: Ashmeen Kaur <57195160+ashmeenkaur@users.noreply.github.com>
  • Loading branch information
kislaykishore and ashmeenkaur authored Nov 26, 2024
1 parent 4e33b30 commit 537ca67
Showing 1 changed file with 10 additions and 1 deletion.
11 changes: 10 additions & 1 deletion docs/troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -68,7 +68,16 @@ This happens when gcsfuse is mounted with http1 client (default) and the applica

### Permission Denied error.

Please refer [here](https://cloud.google.com/storage/docs/gcsfuse-mount#authenticate_by_using_a_service_account) to know more about permissions.(e.g. **Issue**:mkdir: cannot create directory ‘gcs/test’: Permission denied. User can check specific errors by enabling logs with --log-severity=TRACE flags. **Solution**: Provide roles/storage.objectAdmin role on the bucket.) <br/>
Please refer [here](https://cloud.google.com/storage/docs/gcsfuse-mount#authenticate_by_using_a_service_account) to know more about permissions
(e.g. **Issue**:mkdir: cannot create directory ‘gcs/test’: Permission denied. User can check specific errors by enabling logs with --log-severity=TRACE flags.
**Solution** - depending upon the use-case, you can choose one of the following options.
* If you are explicitly authenticating for a specific service account by providing say a key-file, then make sure that the service account has appropriate IAM role for the operation e.g. roles/storage.objectAdmin, roles/storage.objectUser
* If you are using the default service account i.e. not specifying a key-file, then ensure that
* The VM's service account has got the required IAM roles for the operation e.g. roles/storage.objectUser to allow read-write access.
* The VM's scope has been appropriately set. You can set the scope to storage-full to give the VM full-access to the cloud-storage buckets. For this:
* Turn-off the instance
* Change the VM's scope either by using the GCP console or by executing `gcloud beta compute instances set-scopes INSTANCE_NAME --scopes=storage-full`
* Start the instance

### Bad gateway error while installing/upgrading GCSFuse:
`Err: http://packages.cloud.google.com/apt gcsfuse-focal/main amd64 gcsfuse amd64 1.2.0`<br/>`502 Bad Gateway [IP: xxx.xxx.xx.xxx 80]`
Expand Down

0 comments on commit 537ca67

Please sign in to comment.