Update to 4.0.10 kills dashboard

It would be cool if the suggested links would not recommend items from 2019.

Ran dnf update to get new kernel and such and ondemand updates to ondemand-4.0.10 which breaks the dashboard on Rocky 9. I’ve tried rolling back and simply reinstalling ondemand-4.0.8 where we were at but doing so breaks the entire thing. Is there a method to this? Or is there a fix to this occurrence?

Kenny

My solution involved restoring the backup from the previous day. Then I installed dnf versionlock and locked ondemand at 4.08 and whatever else the modules are at. This way I was able to update and patch the OS without updating OnDemand. I’d love to hear if anybody else ran into this problem, or if this is unique, how might I troubleshoot this?

By “breaking” the Dashboard, I mean that none of the menus work any longer..

Browsers tested: Microsoft Edge v147.0.3912.72, Safari (latest), Chrome (latest)

Thanks :slight_smile:

Kenny

Ok, update to this issue. This update is catastrophic to OOD and I’m now in serious need of assistance. The website itself works, as in the menu items work. But when you launch apps, none of them run. Output.log isn’t even created so something broke internally. I’m attaching a “dnf history info ” which shows all packages that were upgraded. I don’t see anything that could have caused such a degradation to the system.

We rolled the system back to a backup before this past Saturday.

tempest-web-update.txt (26.0 KB)

Sorry to hear about your troubles and our delay in a response.

We run 4.1.4 on our EL9 instances, so I don’t know if we can test 4.0 anymore without some work in containers.

Beyond that, I’d have to see some output from /var/log/ondemand-nginx/$USER/error.log to see what could be the issue with submitting jobs.

I was wondering why we weren’t getting upgrades to 4.1.x. One of our grad students just found that the ondemand repo in /etc/yum.repos.d is locked for 4.0 deliveries. I don’t remember ever setting that. No sense in dealing with old versions so we’re not going to spend any energy on that. We’ll upgrade to 4.1 as we can this week.

Kenny

That’s a part of how we distribute our packages. We have different yum base URLs for each version so folks don’t accidentally upgrade multiple versions - i.e., once you install a version, you’ll only get patches which should (should!) be stable and only contain bug and security fixes.

Yeah, I understand that logic. We’ll be sure to keep an eye on future updates. 4.1 looks awesome, guys, nice work :slight_smile: . I’ll mark this as resolved. Thanks Jeff

Kenny