Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix s3csi path & readme #486

Merged
merged 5 commits into from
Aug 12, 2024
Merged

Conversation

bravo325806
Copy link
Contributor

I found no subpath when using s3csi. The readme refdata.type is for using s3csi not s3fs

@ksuderman
Copy link
Contributor

Thanks for the PR. We are investigating as the subPath should be found.

@bravo325806
Copy link
Contributor Author

Hi ksuderman

This error occurs if there are subpath, and I use no subpath only see the byhand managed two folder
Error: failed to create subPath directory for volumeMount "refdata-gxy" of container "galaxy-init-mounts"

I found older versions don't have subpath. If the path of s3 has not changed from the old version to the current version, there should be no need to add a new subpath.

@nuwang
Copy link
Member

nuwang commented Jul 30, 2024

@bravo325806 Can you clarify what you meant by "I found older versions don't have subpath"? Are you trying to upgrade or is this a fresh install?

The subPath is not cvmfs specific and is needed for the bucket too: http://biorefdata.s3-website-ap-southeast-2.amazonaws.com/#galaxy/v1/

@bravo325806
Copy link
Contributor Author

@nuwang Sorry I didn't make this part clear. I used v5.1.0
https://github.com/galaxyproject/galaxy-helm/blob/v5.1.0/galaxy/templates/deployment-web.yaml#L138-L139
Now I have upgrade to v5.15.0, but what I see in the new version is that there is a subpath option https://github.com/galaxyproject/galaxy-helm/blob/v5.15.0/galaxy/templates/deployment-web.yaml#L135-L137

Because values.yaml
The prefix /galaxy/v1/data.galaxyproject.org is already preset
https://github.com/galaxyproject/galaxy-helm/blob/v5.15.0/galaxy/values.yaml#L453

Maybe we can only change values.yaml?

@ksuderman
Copy link
Contributor

@bravo325806 I made a PR to your PR as jobs that are run also mount the refdata PV and should not include the subpath when using the s3csi.

Also, that table of values in the README.md is generated by a script from comments in the values.yaml file, so I updated the comment to match your update to the readme so they don't get lost the next time we generate that table.

As soon as you merge those changes we can go ahead and merge your PR.

@bravo325806
Copy link
Contributor Author

@ksuderman I have merged your PR, Thanks

@nuwang nuwang merged commit 59145bf into galaxyproject:master Aug 12, 2024
2 checks passed
Copy link
Member

@nuwang nuwang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks both for persevering with these fixes + testing. The changes lgtm!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants