Katello minor version update documentation?

On Foreman 3.2 and Katello 4.4 and seen this package arriving to my Foreman server (not for my external proxys): rubygem-katello-

Reading change log for at → katello/CHANGELOG.md at KATELLO-4.4 · Katello/katello · GitHub
So I guess this package (rubygem-katello- takes Katello to

Also reading about upgrades/updates on Upgrading and Updating Foreman
I only seem to come across instructions for Foreman upgrades/updates. For minor Katello updates like this one, any advice or is there documentation I missed for this?

Hi @tedevil,

The general recommendation for minor updates is to yum update and then run foreman-installer.

We had a couple of important bugs that showed up after releasing 4.4.0, so we had to make and releases quickly after.

1 Like

Thanks for the quick reply:
Tried what you suggested but hit an error (trace from production.log):

2022-04-18T14:09:42 [I|app|a0553eca] Started GET "/api/v2/smart_proxies?search=name%3D%22foreman.example.com%22" for at 2022-04-18 14:09:42 +0000
2022-04-18T14:09:42 [I|app|a0553eca] Processing by Api::V2::SmartProxiesController#index as JSON
2022-04-18T14:09:42 [I|app|a0553eca]   Parameters: {"search"=>"name=\"foreman.example.com\"", "apiv"=>"v2", "smart_proxy"=>{}}
2022-04-18T14:09:42 [I|app|a0553eca] Authorized user foreman_api_admin(API Admin)
2022-04-18T14:09:43 [I|app|a0553eca]   Rendering api/v2/smart_proxies/index.json.rabl within api/v2/layouts/index_layout
2022-04-18T14:09:43 [I|app|a0553eca]   Rendered api/v2/smart_proxies/index.json.rabl within api/v2/layouts/index_layout (Duration: 102.6ms | Allocations: 6665)
2022-04-18T14:09:43 [W|app|a0553eca] Action failed
2022-04-18T14:09:43 [I|app|a0553eca] Backtrace for 'Action failed' error (ActionView::Template::Error): Cannot find rabl template 'katello/api/v2/smart_proxies/pulp_info' within registered (["/usr/share/foreman/app/views", "/usr/share/gems/gems/katello-4.4.0/app/views"]) view paths!

Not sure what that was about but seem in the documentation that you can shutdown Foreman first so I did:

foreman-maintain service stop; foreman-installer

This completed without any errors so I just started Foreman back up with:

foreman-maintain service start

That’s how I do it with pretty much every update I do on my foreman servers (major & minor version updates as well as any other update of rpms). I have seen too often in the past that foreman-installer doesn’t always play nicely if foreman is already running… Shutting down foreman before makes sure everything is properly configured and then started in the correct order.


Shouldn’t foreman-installer stop and start services as needed even without stopping them manually first?

Should? Certainly!

Does it? Absolutely not :frowning: (at least not in every case this is required)

This is exactly the issue I was talking about in When should the Installer restart Puma :wink: