Getting Started

… we’re only digesting the info … :yum:

With all the water that has passed under the Foreman bridge, an upgrade from 1.20.1 to the current 1.21.0 would surely be a good idea as to not frustrate the hands that is of help going forward.

Sooo, following the Foreman :: Manual on upgrading, once

    yum upgrade tfm\* ruby\* foreman\*

is run, we’re splashed with:

--> Finished Dependency Resolution
Error: Package: tfm-rubygem-katello-3.10.0-1.el7.noarch (@katello)
           Requires: foreman-webpack-vendor-js(8f1a560ed7b654fe8dba)
           Removing: foreman-1.20.2-1.el7.noarch (@foreman)
               foreman-webpack-vendor-js(8f1a560ed7b654fe8dba)
           Updated By: foreman-1.21.0-1.el7.noarch (foreman)
               Not found
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

Running

yum upgrade tfm\* ruby\* foreman\* --skip-broken

results in:

Packages skipped because of dependency problems:
    foreman-1.21.0-1.el7.noarch from foreman
    foreman-compute-1.21.0-1.el7.noarch from foreman
    foreman-postgresql-1.21.0-1.el7.noarch from foreman
    tfm-ror52-rubygem-i18n-1.4.0-1.el7.noarch from foreman-rails
    tfm-rubygem-gettext_i18n_rails-1.8.0-1.el7.noarch from foreman

On the web interface side og thinfs aka GUI > Administer > About

Under Smart Proxies:

foreman.domain.com    Templates, Pulp, Puppet, Logs, Dynflow, DNS, TFTP, DHCP, Puppet CA, and HTTPBoot   1.21.0

Backend System Status:

Component Status Message
candlepin OK
candlepin_auth OK
foreman_tasks FAIL undefined method `failed?’ for #<Concurrent::Promises::ResolvableFuture:0x000000000bb3eee8>
pulp OK
pulp_auth OK

… meanwhile … I’m pondering rather rebuilding from scratch which would also reaffirm the knowledge gained…

Would a Debian with Katello installation be a reasonable adaptation or an entire new can of worms ?

Katello is still only possible on CentOS/RHEL as some dependencies are only available on them and not Debian.

… ponder terminated ! :no_mouth:

Are there different instructions for upgrading when katello is installed?

Yes, it differs, see Foreman :: Plugin Manuals

Thanks, Dirk. But that seems to be instructions for upgrading katello.

I am already at:
puppet 5.5.10
katello 3.10.0
foreman 1.20.1

I was referring to the problems @peek was having when trying to upgrade to foreman 1.21.0

I’ve been following a few other threads regarding upgrades …

Foreman 1.21 upgrade dependency failures
Katello 3.11 is now available!
Foreman upgrade 1.21 and Katello 3.11
Katello 3.11

Guess I am just a little shy about being in a big hurry to upgrade just yet …
Are there any other considerations I should be worried about?

Katello Upgrade
Upgrading to Foreman 1.21

Smart Proxies ?
SSL Certificates ?
Activation Keys?
Content Host Registrations ?

Other plugins …
OpenSCAP ?
FreeIPA ?

Any known compatibility issues?
I just got this stuff working.
I’m afraid to break it, and having to start over.
Not even sure I would know where to begin again?