Greetings,
First of all I would like to say that in our testing of Katello 4.2 and Foreman 3.0 our proxy sync issues have been solved. We did this as a fresh install and still need to get all of our content and clients moved over but this is very encouraging.
Problem: I would like to verify with the community that when the time comes for us to upgrade from 4.2.1 to 4.2.2 all we need to do is a yum upgrade
Expected outcome: I couldn’t find any documentation for doing a minor upgrade and just would like to verify this is all one needs to do in order to upgrade from 4.2.x to 4.2.x
Foreman and Proxy plugin versions:
root@katello04-> rpm -qa | egrep -i “foreman|katello” | egrep -v -i “ras”
katello-certs-tools-2.8.0-1.el7.noarch
foreman-selinux-3.0.1-1.el7.noarch
katello-common-4.2.1-1.el7.noarch
tfm-rubygem-hammer_cli_foreman_remote_execution-0.2.2-1.fm3_0.el7.noarch
foreman-service-3.0.1-1.el7.noarch
rubygem-foreman_maintain-0.8.10-1.el7.noarch
katello-default-ca-1.0-1.noarch
foreman-cli-3.0.1-1.el7.noarch
tfm-rubygem-hammer_cli_katello-1.1.2-1.el7.noarch
foreman-3.0.1-1.el7.noarch
foreman-installer-3.0.1-1.el7.noarch
katello-repos-4.2.1-1.el7.noarch
katello-4.2.1-1.el7.noarch
foreman-proxy-3.0.1-1.el7.noarch
tfm-rubygem-hammer_cli_foreman-3.0.0-1.el7.noarch
tfm-rubygem-hammer_cli_foreman_tasks-0.0.16-1.fm3_0.el7.noarch
tfm-rubygem-foreman_puppet-1.0.5-1.fm3_0.el7.noarch
foreman-postgresql-3.0.1-1.el7.noarch
tfm-rubygem-foreman-tasks-5.1.0-1.fm3_0.el7.noarch
tfm-rubygem-katello-4.2.1-1.el7.noarch
katello-selinux-4.0.2-1.el7.noarch
foreman-release-3.0.1-1.el7.noarch
foreman-dynflow-sidekiq-3.0.1-1.el7.noarch
foreman-installer-katello-3.0.1-1.el7.noarch
katello-debug-4.2.1-1.el7.noarch
tfm-rubygem-foreman_remote_execution-4.7.0-1.fm3_0.el7.noarch
katello-client-bootstrap-1.7.7-1.el7.noarch
katello-server-ca-1.0-1.noarch
foreman-debug-3.0.1-1.el7.noarch
tfm-rubygem-hammer_cli_foreman_puppet-0.0.3-1.fm3_0.el7.noarch
Distribution and version: CentOS Linux release 7.9.2009 (Core)
Thank you,
Eledor