Problem:
We use Foreman SCC Plugin and have two content-views for SLES 15.1 (1 normal + 1 composite) that are no longer synced to our proxies. This was working fine before we upgraded to Katello 4.3.
Expected outcome:
All content-views are syncing to all proxies
Foreman and Proxy versions:
3.1.3-1
Foreman and Proxy plugin versions:
ansible-collection-theforeman-foreman-3.0.0-2.el7.noarch
foreman-3.1.3-1.el7.noarch
foreman-cli-3.1.3-1.el7.noarch
foreman-debug-3.1.3-1.el7.noarch
foreman-dynflow-sidekiq-3.1.3-1.el7.noarch
foreman-installer-3.1.3-1.el7.noarch
foreman-installer-katello-3.1.3-1.el7.noarch
foreman-openstack-3.1.3-1.el7.noarch
foreman-postgresql-3.1.3-1.el7.noarch
foreman-proxy-3.1.3-1.el7.noarch
foreman-release-3.1.3-1.el7.noarch
foreman-release-scl-7-3.el7.noarch
foreman-selinux-3.1.3-1.el7.noarch
foreman-service-3.1.3-1.el7.noarch
foreman-vmware-3.1.3-1.el7.noarch
katello.a.space.corp-foreman-client-1.0-2.noarch
katello.a.space.corp-foreman-proxy-1.0-5.noarch
katello.a.space.corp-foreman-proxy-client-1.0-2.noarch
rubygem-foreman_maintain-1.0.8-1.el7.noarch
tfm-rubygem-foreman_ansible-7.0.4-1.fm3_1.el7.noarch
tfm-rubygem-foreman_ansible_core-4.2.1-1.fm2_5.el7.noarch
tfm-rubygem-foreman_discovery-19.0.1-1.fm3_1.el7.noarch
tfm-rubygem-foreman_docker-5.0.0-3.fm2_1.el7.noarch
tfm-rubygem-foreman_puppet-2.0.7-1.fm3_1.el7.noarch
tfm-rubygem-foreman_remote_execution-5.0.6-1.fm3_1.el7.noarch
tfm-rubygem-foreman_remote_execution_core-1.4.8-1.el7.noarch
tfm-rubygem-foreman_scc_manager-1.8.20-1.fm3_3.el7.noarch
tfm-rubygem-foreman-tasks-5.2.3-1.fm3_1.el7.noarch
tfm-rubygem-foreman-tasks-core-0.3.6-1.fm2_5.el7.noarch
tfm-rubygem-hammer_cli_foreman-3.1.0-1.el7.noarch
tfm-rubygem-hammer_cli_foreman_bootdisk-0.3.0-2.el7.noarch
tfm-rubygem-hammer_cli_foreman_puppet-0.0.4-1.fm3_1.el7.noarch
tfm-rubygem-hammer_cli_foreman_remote_execution-0.2.2-1.fm3_0.el7.noarch
tfm-rubygem-hammer_cli_foreman_tasks-0.0.17-1.fm3_1.el7.noarch
ansible-collection-theforeman-foreman-3.0.0-2.el7.noarch
foreman-debug-3.1.3-1.el7.noarch
foreman-installer-3.1.3-1.el7.noarch
foreman-installer-katello-3.1.3-1.el7.noarch
foreman-proxy-3.1.3-1.el7.noarch
foreman-proxy-content-4.3.1-1.el7.noarch
foreman-release-3.1.3-1.el7.noarch
foreman-release-scl-7-3.el7.noarch
foreman-selinux-3.1.3-1.el7.noarch
gedapvl05.a.space.corp-foreman-proxy-1.0-11.noarch
gedapvl05.a.space.corp-foreman-proxy-client-1.0-11.noarch
rubygem-foreman_maintain-1.0.8-1.el7.noarch
tfm-rubygem-foreman_ansible_core-4.2.1-1.fm2_5.el7.noarch
tfm-rubygem-foreman_remote_execution_core-1.4.8-1.el7.noarch
tfm-rubygem-foreman-tasks-core-0.3.6-1.fm2_5.el7.noarch
Distribution and version:
CentOS 7.9
Other relevant data:
We use the Foreman SCC Plugin to sync SLES content to Katello. We see the following error when manually syncing content in the Foreman UI:
: Failing row contains (94c9e187-2a86-452f-be04-c203fe9f1f34, SUSE-SLE-Module-Legacy-15-SP1-2020-1059, null, This update for open-iscsi fixes the following issues: - Avoid …, null, maint-coord@suse.de, stable, Recommended update for open-iscsi, , 1, recommended, moderate, , SUSE Updates SLE-Module-Legacy 15-SP1 x86 64, , , 42e0608bd70f9fa94437d89c7f014f8bdee4ec1bb230e96b3750bf2172cdd70d, f). Plus 3 more errors
I thought the problem might be related to the content-view itself so I created a new content-view called "Linux SLES 15.1 i2r1.1) and tried to sync but the problem is the same. In the Smart Proxy overview we can see that the content-views are not synced.