Dashboard not showing all apps for user about ood-documentation HOT 4 CLOSED

I would check the file permissions of those applications. A quick read of this suggests that they cannot read the directory for jupyter.

from ood-documentation.

from ood-documentation.

I suspect that something in the user's environment is being read

OnDemand (the web app portion) does not read the users environment. That is, it doesn't read/execute a ~/.bashrc or anything like that. (the jobs the web app will submit start SHELL environments, but that's during the jobs execution, not within the per user nginx - PUN). The environments should be uniform across all user PUNs.

What's not uniform across all user PUNs are the UID and GID(s) the application boots up with. The web application will search all the directories in /var/www/ood/apps/sys/ if it's a system installed application. If it can read the children directories here then every directory will become an 'app'. This is why I'm wondering about file permissions.

File permissions are the primary mechanism we use to hide or disable applications.
I'd ask these other questions:

• Is Jupyter a system installed application or is it being shared from someone? If it's being shared, check those permissions.
• double check for any FACLs that may be applied to Jupyter. You may see that it's 755 readable, but somehow there's a FACL that disables it for this user.
• There's an edge case here where the Jupyter application is using a cluster the user can't see. And so, we're not showing the app because the user can't see the cluster it uses. Check the cluster.d files for the cluster this app users. Check to see if this user can read those cluster files as well.
  • These cluster files also provide a mechanism to enable and disable users through groups. Check to see if these cluster.d files have an acl configurations that could be blocking this user.

from ood-documentation.

This does not seem to be a documentation ticket, so I'm closing it now. Should you continue to have issues, I can reopen or you can open a topic on our discourse instance: https://discourse.openondemand.org/

from ood-documentation.