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

Open OnDemand UI Issue: Newly Mounted AWS S3 Bucket Not Visible in Files Section #3733

Open
mharini opened this issue Aug 16, 2024 · 4 comments
Labels
Milestone

Comments

@mharini
Copy link

mharini commented Aug 16, 2024

Hi,

We are currently encountering an issue with OnDemand when attempting to view a mounted S3 bucket in the UI. A new bucket was created with the appropriate permissions and added to the user groups. We run a cron job to mount/unmount the S3 buckets in periodic basis, based on user group and permissions. The bucket appears in the mounted path, and we can list the files from the cluster shell. However, they are not accessible from the OnDemand UI. While restarting the OnDemand service resolved the issue, we are seeking a solution that doesn't require a restart.

Any inputs would be great to resolve this issue.
Screenshot 2024-08-16 at 3 40 31 PM

@osc-bot osc-bot added this to the Backlog milestone Aug 16, 2024
@johrstrom
Copy link
Contributor

While restarting the OnDemand service resolved the issue, we are seeking a solution that doesn't require a restart.

I'd guess it's an issue of when and how it's mounted. If it's mounted as a filesystem just like any other NFS drive that's been mounted I can only think there's a race condition of some kind. Like we're trying to access it when it's not available yet.

How and when is it mounted?

@mharini
Copy link
Author

mharini commented Aug 19, 2024

The S3 buckets are mounted using s3fs using a cron job running on a periodic basis, to identify if any new buckets or permissions or groups are added/modified.

We also see that "Restart Web Server" in the help option fixes the issue without restarting the all of the ondemand.

@mharini
Copy link
Author

mharini commented Aug 23, 2024

We have modified the cron job to kill the nginx process for a specific user using pid whenever there is a change in group or user.

We also identified comments in the existing code base that the web server should be restarted automatically when there is a change in the group or user. Any additional configurations to be done for this to happen?

@johrstrom
Copy link
Contributor

Any additional configurations to be done for this to happen?

I don't think so. IIRC the app checks to see if any groups have changed then provides a button for the user to restart? But that's just from memory.

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

No branches or pull requests

3 participants