Hi,
We would first like to extend our gratitude to the community for Foreman and Katello. So far it has been performing well and there are things that we like about it much more than Spacewalk.
There is one kind of complex problem we have run into that is a sync problem from the main servers out to the smart proxies. Clients that hit the main servers direct, and thereby bypass the proxies, do not have this issue.
Problem: Whenever we make a change to a Content View that contains the CentOS 7 base repo it won’t sync to our Smart Proxies. Clients connected to the smart proxy will return a 404 for the base repo. All other repos are fine.
Expected outcome:. The Base Repo should sync without the workaround we do which is regenerate metadata for the CentOS 7 base repo, regenerate metadata for the Content View and then do a complete sync to our Smart Proxies. NB: an optimized sync does not work for the workaround, we have to do the full sync.
Foreman and Proxy versions:
Main Server:
root@katello02-> rpm -qa | egrep -i “foreman|katello”
katello-common-3.18.2-1.el7.noarch
foreman-installer-katello-2.3.4-1.el7.noarch
foreman-installer-2.3.4-1.el7.noarch
foreman-release-2.3.4-1.el7.noarch
tfm-rubygem-hammer_cli_foreman_bootdisk-0.3.0-1.el7.noarch
foreman-dynflow-sidekiq-2.3.4-1.el7.noarch
katello-client-bootstrap-1.7.5-1.el7.noarch
rubygem-foreman_maintain-0.7.9-1.el7.noarch
tfm-rubygem-foreman-tasks-core-0.3.4-1.fm2_1.el7.noarch
tfm-rubygem-katello-3.18.2.1-1.el7.noarch
pulp-katello-1.0.3-1.el7.noarch
katello-3.18.2-1.el7.noarch
katello-selinux-3.5.0-1.el7.noarch
foreman-2.3.4-1.el7.noarch
katello-server-ca-1.0-1.noarch
tfm-rubygem-hammer_cli_foreman_tasks-0.0.15-1.fm2_2.el7.noarch
foreman-debug-2.3.4-1.el7.noarch
katello-repos-3.18.2-1.el7.noarch
tfm-rubygem-foreman_remote_execution_core-1.4.0-1.el7.noarch
tfm-rubygem-foreman-tasks-3.0.5-1.fm2_3.el7.noarch
tfm-rubygem-hammer_cli_foreman-2.3.2-1.el7.noarch
foreman-postgresql-2.3.4-1.el7.noarch
foreman-selinux-2.3.4-1.el7.noarch
foreman-service-2.3.4-1.el7.noarch
foreman-proxy-2.3.4-1.el7.noarch
katello-default-ca-1.0-1.noarch
tfm-rubygem-hammer_cli_katello-0.24.3-1.el7.noarch
foreman-cli-2.3.4-1.el7.noarch
tfm-rubygem-foreman_remote_execution-4.2.2-1.fm2_3.el7.noarch
katello-debug-3.18.2-1.el7.noarch
katello-certs-tools-2.7.3-1.el7.noarch
tfm-rubygem-hammer_cli_foreman_docker-0.0.7-1.el7.noarch
[~]
Proxy:
rpm -qa | egrep -i ‘foreman|katello’ | grep -i -v aws
katello-default-ca-1.0-1.noarch
katello-repos-3.18.4-1.el7.noarch
katello-certs-tools-2.7.3-1.el7.noarch
foreman-installer-2.3.5-1.el7.noarch
katello-debug-3.18.4-1.el7.noarch
katello-server-ca-1.0-1.noarch
foreman-release-2.3.5-1.el7.noarch
rubygem-foreman_maintain-0.7.10-1.el7.noarch
foreman-proxy-content-3.18.4-1.el7.noarch
katello-client-bootstrap-1.7.5-1.el7.noarch
foreman-debug-2.3.5-1.el7.noarch
foreman-installer-katello-2.3.5-1.el7.noarch
katello-common-3.18.4-1.el7.noarch
foreman-proxy-2.3.5-1.el7.noarch
Distribution and version:
CentOS Linux release 7.9.2009 (Core)
Other relevant data:
Katello logs have:
Katello::Errors::PulpError: PLP0000: Importer indicated a failed response
Seems to be related to these posts:
https://pulp.plan.io/issues/8176
Any help you folks could provide would be most appreciated.
Cheers,
Eledor