Custom Product does not show up anymore in CV

Support
1

Problem:
I have an CCV with CentOS7, EPEL7, Zabbix RHEL 7

Product = Zabbix
Repo’s = RHEL 7 Zabbix Repo, RHEL8 zabbix Repo

Activation key is setup correct with Subscription and enabled Repository set

Seems Problem is only with RHEL 7 Zabbix Repo
Around 30 host already registered, they can see the Zabbix Repo
New Hosts added via Activation Key, does not see the RHEL 7 Zabbix Repo

It doesnt matter, how i try it, i change ContentView from Host to only “Zabbix RHEL 7 CV” and subscription manager telling me, no repos enabled

Zabbix RHEL 8 CV is working

Already tryed to remove Repo from Contentview, publish new version, add repo to content view, same issue

How can i trouble shoot this further?
i added around 30 Hosts in the past few days and everything was fine

foreman-postgresql-2.4.1-1.el8.noarch
foreman-release-2.4.1-1.el8.noarch
foreman-service-2.4.1-1.el8.noarch
foreman-dynflow-sidekiq-2.4.1-1.el8.noarch
foreman-client-release-2.4.1-1.el8.noarch
foreman-2.4.1-1.el8.noarch
foreman-installer-2.4.1-1.el8.noarch
foreman-cli-2.4.1-1.el8.noarch
foreman-debug-2.4.1-1.el8.noarch
foreman-proxy-2.4.1-1.el8.noarch
foreman-installer-katello-2.4.1-1.el8.noarch
foreman-selinux-2.4.1-1.el8.noarch

rubygem-pulp_2to3_migration_client-0.7.0-1.el8.noarch
rubygem-pulp_deb_client-2.9.1-1.el8.noarch
python3-pulp-rpm-3.10.0-1.el8.noarch
rubygem-pulp_file_client-1.5.0-1.el8.noarch
rubygem-pulp_certguard_client-1.0.3-1.el8.noarch
rubygem-pulp_rpm_client-3.10.0-1.el8.noarch
python3-pulp-deb-2.9.2-1.el8.noarch
pulpcore-selinux-1.2.4-1.el8.x86_64
rubygem-pulp_container_client-2.2.0-1.el8.noarch
rubygem-pulpcore_client-3.9.0-1.el8.noarch
pulp-client-1.0-1.noarch
python3-pulp-file-1.5.0-1.el8.noarch
python3-pulp-certguard-1.1.0-1.el8.noarch
python3-pulpcore-3.9.1-2.el8.noarch
rubygem-smart_proxy_pulp-2.1.0-3.fm2_2.el8.noarch
rubygem-pulp_ansible_client-0.6.0-1.el8.noarch
python3-pulp-container-2.2.2-1.el8.noarch

thanks alot

2

when i force subscitiopn manager to register again, Hosts who still have worked, do not work see zabbix RHEL 7 afterwards

very wierd

3

OK, its ok now

i removed Zabbix RHEL 7 from CCV and published new version + promote
i deleted every CV +CCV where zabbix RHEL7 was published
deleted Repository in Zabbix Product

added Repo to zabbix product via Repo Discovery
Did advanced Sync > Conplete Sync

added Zabbix RHEL7 repo to CCV
published and promoted new version

vioala… the Zabbix RHEL 7 is back again

any idea how to figure out why this happened?

4

The next time you hit this situation try the following command on your hosts
subscription-manager refresh
yum repolist

Subman I believe checks in every 4 hours for updated content. That refesh command should resolve any caching issues.