Good afternoon.
We are in a testing situation about Open OnDemand upgrades to version 4.0.0 in one of our development environments.
We have managed to upgrade from a fully functional 3.0.3 environment to 4.0.0.0.
The problems come when two of the applications that were working such as the “Active Jobs” and the “SSH Console” are now not working.
In the case of the Active Jobs screen, the jobs that are launched to the cluster are not reflected regardless of their status (I attach an image where you can see that the resource monitor detects the use of the machines and how from the console you can also see it.
In the case of the Shell, when we want to open a session from “Clusters” right now we get a connection terminated message. Is there any configuration change between these two versions that may be affecting these tools? (Let’s remember that all this worked correctly before the version change.)
Hello again, I have updates on these bugs corresponding to v4.
After doing several tests and checking if these errors occurred in a direct installation of v4 on a clean machine (no errors), I came to the conclusion that the error was due to upgrading an environment from version 3 to 4.
For this reason I have made a debugging process removing packages from version 3 before installing version 4, this is because if before performing the steps detailed in tutorial you run a “yum remove ondemand*” the errors of version 4 did not appear.
After many tests removing packages individually we have seen that the package that generates the error is “ondemand-apache”, if before executing the steps for the upgrade this removal is done, the update from version 3 to 4 is done correctly and both problems reported in the thread disappear.
I don’t know very well what could be happening here, maybe the regeneration of the apache files is not working correctly in this particular case, let me know if you know what could be happening.
I had this exact issue upgrading from 3.x to 4.x a few weeks ago. We ended up rolling back to ver 3 so it’s great you found a potential work around! Thanks for posting that update.
Maybe there can be an update on the upgrade logic in the packages to account for this ondemand-apache issue.
Hi Jeff, sorry for the delay on our part.
I’m a bit busy these days, but I could try to replicate the upgrade process once again (we have a rollback in our environment) and collect the log data if you need it.
If/when you do yea just send the logs. I imagine it is an issue with httpd and that you need to update it because of a patch we made to support higher httpd versions.
Hello again Jeff.
Today we have been trying to replicate the error processes once again to give you some information. The thing is that now the upgrade process takes us to version 4.0.1 (recently released). When we tried to replicate the errors one more time we could not. So from what I am seeing these problems were fixed in this new 4.0.1 version.
I will mark this as resolved for now as we are not encountering any other major problems, thank you for your help once again.
Best regards.
