Can’t upgrade from Foreman 3.2 to 3.3. See Other relevant data for more context.
To have a foreman 3.3 server after following upgrade instructions
Foreman and Proxy versions:
Foreman 3.2 w/Katello 4.4
Other relevant data:
Hello, I’m relatively new to Foreman and I’ve been tasked to upgrade our production server from 3.2 to 3.5. Reading through the documentation, I need to upgrade to 3.3 and 3.4 before I can upgrade to 3.5.
I’ve setup a development server to figure out the process, but I’ve had very little luck with anything I’ve tried. I’m running Rocky Linux 8.7 for the OS and I followed these instructions to get a clean install of Foreman 3.2/Katello 4.4…
That installs without issue and I am able to login to my newly created instance of Foreman 3.2. From there, I proceeded to follow these instructions to upgrade to version 3.3…
I don’t have anything modified, nor do I care to create a backup of the development server, so I skip to step 6. Everything executes fine, until I get to step 10, ‘yum -y update’. It errors out with this message,
Error: Problem: package rubygem-qpid_proton-0.37.0-1.el8.x86_64 requires libruby.so.2.5()(64bit), but none of the providers can be installed - cannot install the best update candidate for package rubygem-qpid_proton-0.35.0-1.el8.x86_64 - package ruby-libs-2.5.9-110.module+el8.6.0+992+fc951c18.x86_64 is filtered out by modular filtering (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
I figured skipping broken wouldn’t be the best idea, so I decided to look into migrating my 3.2 server to a fresh install of Foreman 3.5. Before I got started, I wanted to backup my production server, just in case. Here, I ran into more issues. I followed the instructions from here…
The first issue I ran into was.
No such file or directory - /etc/foreman-installer/scenarios.d/last_scenario.yaml (Errno::ENOENT)
That was easily resolved by creating that file. However, I was greeted with more errors that required me to white-list a bunch of things that seemed critical. After running into road blocks using ‘foreman-maintain’, I found that I could make a backup with ‘foreman-rake db:dump’. But that did not seem to have the outcome I was anticipating. I am able to backup and restore on my development server of Foreman => 3.2.
So now, I am at my wits end. Can anyone tell me what I am doing wrong and how to get on the right track?