When a user starts an interactive session, while it’s in the queue Ondemand just shows a basic message saying that it has yet to start running. An issue we often have is that users will attempt to run a job that overruns a QOS limit, so the job will never run. Using something like squeue to inspect the job’s reason field will show that it is held for a reason like “QOSMaxMemoryPerUser”, but to a user looking on Ondemand it’s not clear if their job is queued because it is simply waiting or because it has hit something like a QOS limit. Is there a simple way to do something like displaying the job’s reason field in the UI?
Hello and welcome!
I am going to guess by “simple way” you mean “supported and documented configuration” 
which we do not currently have for what you are asking.
Poking around to see if this is easily scripted or if we can adjust OOD easily, it isn’t as simple as I’d hoped. The issue here is we need to get some info from the scheduler around this, and currently the OodCore::Job::Info object doesn’t seem to provide the reason field at all either, so currently OOD has no way to handle this info and actually pass it back to use as you are asking.
Hello,
Thanks for the quick response! I guess we’ll have to find another way to solve this problem. Possibly making the message about verifying QOS limits in larger font. 