Foreman server has automatically upgraded the RPMs to the
new 3.18.1 release and restarted services.
The documentation the release notles link to only mentions major
upgrades; do I also need to run foreman-installer on these
minor/point-release updates too?
Expected outcome:
Understand the point release / minor upgrade process
I recommend to always run it after a package upgrade. On the one side if something changed in foreman package it could be needed, on the other side if apache httpd gets updated the installer needs to be run to bring back the structure from the puppet modules. So having as update job something like dnf update -y; foreman-installer is a good idea.
Thanks for the info; Apache updates is a good point or perhaps more likely the risk of any of the other config files added under /etc/httpd as ours has been somewhat customised.
Thanks for the info - I understand with open source projects resources are often limited, however I would like to point out that the release notes for 3.18.1 link to the upgrade docs, not the update docs you pointed me to.
Iām not sure where the update docs are linked from, however I think the best thing would be if theyāre added to the overall manual. Iāll have a look and see if thereās some way I can contribute or suggest that approach.
The source of the one you are referencing lives in the theforeman.org project. When I was adding the release notes for 3.18.1, I did not touch the āUpgrade to 3.18ā section at all. The Upgrade section was created at the time when we branched 3.18 and has stayed untouched since then.
I must admit that Iām not the best person to talk to about documentation, so perhaps someone from the Documentation crowd can jump in and share their insights on this.