Fix issue with s3fs mount randomly taking time using IAM credentials on Private VPC clusters #259
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ashimagarg27
approved these changes
Sep 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe your changes
I noticed that during S3FS mount using IAM credentials and private iam endpoint for fetching token with
-o ibm_iam_auth -o ibm_iam_endpoint=https://private.iam.cloud.ibm.comparams, s3fs fuse randomly used to still use https://iam.cloud.ibm.com/ for fetching token which failed. Later it eventually used private iam endpoint to fetch the token. Due to this issue, s3fs fuse used to take around 4-10 minutes to come to Running state.Issue ticket number and link
Checklist before requesting a review