Foreman katello scenary dont have any --content-type to repositorys

Hello,

Dont know if someone have the same error, but when i want to create new repo i cant select any content type.

hammer repository create --organization ‘X’ --product ‘CentOS7’ --name ‘CentOS 7 OS’ --label ‘CentOS7_OS’ --content-type ‘yum’ --download-policy ‘on_demand’ --gpg-key-id ‘2’ --url ‘CentOS Mirror’ --mirror-on-sync ‘no’
Could not create the repository:
Validation failed: Content type is not enabled. must be one of the following:

Foreman and Proxy versions:
3.0.0-1
Foreman and Proxy plugin versions:
3.0.0-1

Red Hat Enterprise Linux Server release 7.9 (Maipo)

This is a known bug, we’re taking care of it. More information from other users is here: Undefined method pulp3_skip_publication error after upgrade - #32 by Justin_Sherrill

Seems a problem with smart proxy, i don0t have indepedent installation of smart proxy.
Is just the same server. That could be possible?

2021-10-27 17:57:35 [ERROR ] [configure] Error making POST request to Foreman at https://repouxlg01.example.com/api/v2/smart_proxies: Unable to communicate with the proxy: ERF12-2530 [ProxyAPI::ProxyException]: Unable to detect features ([RestClient::Exceptions::ReadTimeout]: Timed out reading data from server) for proxy https://repouxlg01.example.com:9090/v2/features Please check the proxy is configured and running on the host.
2021-10-27 17:57:35 [ERROR ] [configure] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[repouxlg01.example.com]/ensure: change from ‘absent’ to ‘present’ failed: Error making POST request to Foreman a

Anybody found solution for this issue?
I have done a fresh setup and now stuck at this.
“Validation failed: Content type is not enabled. must be one of the following:”

I am on Foreman 3.4 and Katello 4.6.

We are hitting the same issue on the latest version of foreman and pulp”

[root@10-221-150-61 ~]# rpm -qa | grep pulp
python3.12-pulp-glue-0.32.3-1.el9.noarch
python3.12-pulpcore-3.73.14-2.1.el9.noarch
pulpcore-selinux-2.1.0-1.el9.x86_64
python3.12-pulp-container-2.24.2-2.el9.noarch
python3.12-pulp-rpm-3.29.7-2.el9.noarch
python3.12-pulp-deb-3.5.3-1.el9.noarch
python3.12-pulp-ansible-0.24.7-1.el9.noarch
python3.12-pulp-python-3.13.5-1.el9.noarch
rubygem-smart_proxy_pulp-3.4.0-1.fm3_13.el9.noarch
[root@10-221-150-61 ~]# rpm -qa | grep foreman
foreman-release-3.16.1-1.el9.noarch
rubygem-foreman_maintain-1.13.6-1.el9.noarch
foreman-installer-3.16.1-1.el9.noarch
foreman-installer-katello-3.16.1-1.el9.noarch
foreman-proxy-content-4.18.1-1.el9.noarch
foreman-proxy-3.16.1-1.el9.noarch

2025-12-19T19:39:38 [I|bac|1282c10c] Task {label: Actions::Katello::CapsuleContent::Sync, id: 612cfccb-faa9-484f-9583-610349452ef3, execution_plan_id: 87353333-727b-42fb-a410-263dddc299eb} state changed: stopped  result: error
2025-12-19T19:39:38 [E|app|1282c10c] RuntimeError: Cannot find repository type yum, is it enabled?

This might happen if the pulpcore services are running into some issues on the capsule or the ordering of certain calls we make to determine available plugins on the smart proxy.

Would you mind restarting services on the proxy with foreman-maintain service restart and see if that resolves it.

Another thing worth checking is if the yum plugin was enabled during installation on the proxy. This should be true by default unless overridden.

cat /etc/foreman-installer/scenarios.d/capsule-answers.yaml | grep "enable_yum"

The issue is that both servers in our high availability were set to mirror: false as soon as we set one to mirror: true it worked.