Upgrade Open OnDemand from version 3.0.3 to 3.1.9 in Rocky Linux 8.8

Hi,

I would like to upgrade Open OnDemand from version 3.0.3 to 3.1.9 in Rocky Linux 8.8. If I follow the ‘Upgrade directions’ for ‘RedHat/Rocky Linux/AlmaLinux 8’ in the following link, is that OK for the upgrade? Is there anything that I need to pay attention to during the upgrade?

https://osc.github.io/ood-documentation/latest/release-notes/v3.1-release-notes.html

Additionally, are there any features or functions from version 3.0.3 that are lost after upgrading?

Thanks

The release notes (that you’ve linked) say there’s only 1 breaking change. While you’re able to configure this, most sites hadn’t (I’m not sure if any did in fact). So there is that 1 item you need to take care of, if you did indeed use the configuration at all. If you didn’t, then you should be all good.

I would have to say though, that I’m a bit alarmed by this issue below that I cannot replicate. OSC is going to production tomorrow, so I guess we’ll know more at that time, maybe, as again, I’m not able to replicate that issue specifically at OSC.

Hi Jeff,

Thanks for your reply.

The Shell Access feature is most important for us. Could you please recommend a specific version under 3.1 (e.g., v3.1.1, 3.1.2, etc.) for the upgrade?

Furthermore, is there a fallback procedure in case the upgrade fails? For example, if I discover that the upgrade from v3.0.3 to v3.1.2 has failed, can I revert back to the original version, v3.0.3?

Hi Jeff/Support,

Could you please check if you can answer the above questions?

Many thanks

Shell access works for 3.1.9 - you just have to have the right httpd version. I’ve updated the release notes for the same. You should always be able to rollback or install a specific version.

https://osc.github.io/ood-documentation/latest/release-notes/v3.1-release-notes.html#advanced-httpd-support

Hi Jeff,

Thanks for your prompt reply. I have two questions:

  1. Do the Open OnDemand v3.1.9 packages also include the right version of the httpd package, eliminating the need for me to install the httpd individually?

  2. I have read the documentation at the provided link, however, I am unable to find the rollback procedure. Could you please provide me with the rollback procedure so that I can revert to v3.0.3 in case the upgrade to v3.1.9 fails?

Thanks

  1. No they don’t require the specific package. You may need to issue dnf update httpd or similar.
  2. I’m pretty sure the steps to rollback to 3.0 are just the steps to install 3.0.

Hi Jeff,

According to the provided link, does it indicate that the httpd version needs to be updated to at least 2.4.37-65 or above for Rocky Linux 8.8?

Thanks

Hi Jeff,

Would you please check if you can answer the above question?

Many thanks

Yes the link says that you need 2.4.37-65 or above for Rocky Linux 8.8.

Jeff, many thanks!!!

Hi Jeff,

I observed that the latest version for Open Ondemand is version 3.1.10. However, I want to upgrade to version 3.1.9 only.

Referring to the procedure in the upgrade direction for the web link v3.1 Release Notes — Open OnDemand 3.1.0 documentation

  1. sudo yum install -y https://yum.osc.edu/ondemand/3.1/ondemand-release-web-3.1-1.el8.noarch.rpm
  2. sudo dnf module reset nodejs
    sudo dnf module enable nodejs:18
    sudo dnf module reset ruby
    sudo dnf module enable ruby:3.1
  3. sudo yum clean all
    sudo yum update ondemand

For the command “yum update ondemand”, I guess this command will directly upgrade to v3.1.10. For this, how to update to specific version (3.1.9) using yum update command?

I think this is what you want. dnf/yum can install specific packages you just have to specify the version.

dnf install ondemand-3.1.9-1.el9

This command should show you what versions are available.

dnf --showduplicates list  ondemand

Jeff, many thanks!!!

Hi Jeff,

I checked that the latest version of httpd, 2.4.37-56, is only available for Rocky 8.8. In order to update httpd to at least version 2.4.37-65 or above for the ondemand version 3.1.9, I would have to upgrade the Rocky OS. However, I don’t want to do this, so I will choose ondemand version 3.1.7 for the upgrade. But I have the following questions:

  1. Will version 3.1.7 fix the SSH Shell App 5-minute inactivity timeout issue?

  2. Will Shell Access stop working after I upgrade to version 3.1.7 with httpd version 2.4.37-56?

Thanks

I’m pretty sure you can pull the 8.8 version on an 8.4 system (or any 8.x).

  1. There are no limits on the ssh inactivity in 3.1.7. That was the bug, not a feature though.
  2. It should continue to work. Or at least it does on our systems. I’m still looking into why it’s stopped working on some folks’ systems.

Hi Jeff,

After upgrading to Open OnDemand version 3.1.7, I was able to upload a large folder containing 5263 files and 24 folders to my home directory using the ‘Files’ app. However, I consistently encounter issues when attempting to download the same large folder to my desktop device using the ‘Files’ app.

I have attached the Nginx error log for your reference. Additionally, I can download and upload smaller folders (65 files and 25 folders) without any problems. In version 3.0.3, I had no issues with downloading or uploading the large folder.

Similar to version 3.0.3, I have configured OOD_DOWNLOAD_DIR_TIMEOUT_SECONDS=“300” in /etc/ood/config/apps/dashboard/env for version 3.1.7. Despite this configuration, the download issue persists. Could you please assist in investigating this matter?
files_download_error.txt (7.4 KB)
Thank you.

Hi Jeff/Support,

Do you have any update for this problem for v3.1.7? Thanks

Hi Jeff/Support,

Would you please see if there is any solution for this problem for v3.1.7? Thanks

I don’t know what issues you could be having trying to download. I see the error you have in the text, client disconnected but I’m not entirely sure what that means in this context. Is it the http client that’s disconnected or something about the stream?

OOD_DOWNLOAD_DIR_TIMEOUT_SECONDS controls how long to wait to while trying to ascertain the size of the folder. Here in your output you can see the command we run - timeout 300 du -cbs. OOD_DOWNLOAD_DIR_TIMEOUT_SECONDS controls how long the timeout in this command is.

App 294666 output: [2024-11-28 15:51:19 +0800 ]  INFO "execve = [\"timeout\", \"300s\", \"du\", \"-cbs\", \"/hpchome/test/Test1d_multiple_files_and_folders_in_a_folder/Data\"]"