Foreman Proxy Couldn't enable 'ansible'

Support
,
#1

Problem:
After upgrading to Foreman 1.24.2 the ansible proxy plugin can’t be enabled any longer.
Expected outcome:
That the ansible plugin is enabled.

Foreman and Proxy versions:
Foreman 1.24.2
foreman-proxy 1.24.2-1
Foreman and Proxy plugin versions:
ruby-smart-proxy-ansible 3.0.0-2
ruby-smart-proxy-dhcp-remote-isc 0.0.4-1
ruby-smart-proxy-dynflow 0.2.3-1
ruby-smart-proxy-dynflow-core 0.2.2-1
ruby-smart-proxy-remote-execution-ssh 0.2.1-1
Distribution and version:
Debian 9
Other relevant data:
proxy.log

2020-02-24T10:36:23  [D] 'dynflow' ports: 'http': false, 'https': true
2020-02-24T10:36:23  [D] 'ansible' settings: 'ansible_working_dir': ~/.foreman-ansible, 'enabled': true
2020-02-24T10:36:23  [D] 'ansible' ports: 'http': true, 'https': true
2020-02-24T10:36:23  [D] 'ssh' settings: 'async_ssh': false (default), 'enabled': https, 'kerberos_auth': false (default), 'local_working_dir': /var/tmp (default), 'remote_working_dir': /var/tmp (default), 'ssh_identity_key_file': /var/lib/foreman-proxy/ssh/id_rsa_foreman_proxy, 'ssh_user': root (default)
2020-02-24T10:36:23  [D] 'ssh' ports: 'http': false, 'https': true
2020-02-24T10:36:23  [D] 'tftp' settings: 'enabled': https, 'tftp_connect_timeout': 10 (default), 'tftp_dns_timeout': 10 (default), 'tftp_read_timeout': 60 (default), 'tftproot': /srv/tftp
2020-02-24T10:36:23  [D] 'tftp' ports: 'http': false, 'https': true
2020-02-24T10:36:23  [D] 'dhcp' settings: 'enabled': true, 'ping_free_ip': true (default), 'server': 127.0.0.1 (default), 'subnets': [] (default), 'use_provider': dhcp_isc (default)
2020-02-24T10:36:23  [D] 'dhcp' ports: 'http': true, 'https': true
2020-02-24T10:36:23  [D] 'puppetca' settings: 'enabled': https, 'puppet_version': 5.5.16, 'use_provider': ["puppetca_hostname_whitelisting", :puppetca_puppet_cert]
2020-02-24T10:36:23  [D] 'puppetca' ports: 'http': false, 'https': true
2020-02-24T10:36:23  [D] 'puppet' settings: 'enabled': https, 'puppet_version': 5.5.16, 'use_provider': [:puppet_proxy_puppet_api]
2020-02-24T10:36:23  [D] 'puppet' ports: 'http': false, 'https': true
2020-02-24T10:36:23  [D] 'logs' settings: 'enabled': https
2020-02-24T10:36:23  [D] 'logs' ports: 'http': false, 'https': true
2020-02-24T10:36:23  [D] 'httpboot' settings: 'enabled': true, 'http_port': , 'https_port': 8443, 'root_dir': /srv/tftp
2020-02-24T10:36:23  [D] 'httpboot' ports: 'http': true, 'https': true
2020-02-24T10:36:23  [D] Providers ['dhcp_isc'] are going to be configured for 'dhcp'
2020-02-24T10:36:23  [D] Providers ['puppetca_hostname_whitelisting', 'puppetca_puppet_cert'] are going to be configured for 'puppetca'
2020-02-24T10:36:23  [D] Providers ['puppet_proxy_puppet_api'] are going to be configured for 'puppet'
2020-02-24T10:36:23  [D] 'dhcp_isc' settings: 'blacklist_duration_minutes': 1800 (default), 'config': /etc/dhcp/dhcpd.conf (default), 'leases': /var/lib/dhcp/dhcpd.leases, 'leases_file_observer': inotify_leases_file_observer, 'omapi_port': 7911, 'ping_free_ip': true, 'server': 127.0.0.1, 'subnets': [], 'use_provider': dhcp_isc
2020-02-24T10:36:23  [D] 'puppetca_puppet_cert' settings: 'puppet_version': 5.5.16, 'ssldir': /etc/puppetlabs/puppet/ssl, 'use_provider': ["puppetca_hostname_whitelisting", :puppetca_puppet_cert]
2020-02-24T10:36:23  [D] 'puppetca_hostname_whitelisting' settings: 'autosignfile': /etc/puppetlabs/puppet/autosign.conf, 'puppet_version': 5.5.16, 'use_provider': ["puppetca_hostname_whitelisting", :puppetca_puppet_cert]
2020-02-24T10:36:23  [D] 'puppet_proxy_puppet_api' settings: 'api_timeout': 30 (default), 'classes_retriever': apiv3, 'environments_retriever': apiv3, 'puppet_ssl_ca': /etc/puppetlabs/puppet/ssl/certs/ca.pem, 'puppet_ssl_cert': /etc/puppetlabs/puppet/ssl/certs/svlicm01001.wago.local.pem, 'puppet_ssl_key': /etc/puppetlabs/puppet/ssl/private_keys/svlicm01001.wago.local.pem, 'puppet_url': https://svlicm01001.wago.local:8140, 'puppet_version': 5.5.16, 'use_provider': [:puppet_proxy_puppet_api]
2020-02-24T10:36:23  [I] Successfully initialized 'dynflow'
2020-02-24T10:36:23  [E] Couldn't enable 'ansible'
2020-02-24T10:36:23  [I] Successfully initialized 'ssh'
2020-02-24T10:36:23  [I] Successfully initialized 'foreman_proxy'
2020-02-24T10:36:23  [I] Successfully initialized 'tftp'
#2

I was able to find out that this is caused by ForemanTasksCore::Runner::Parent not be defined.
This is needed by ruby-foreman-ansible-core since version 3 for foreman 1.22. But ruby-foreman-tasks-core was not updatet on debian and the available packeges dose not provide this class.

How can I upgrade this package on debian if its not in the repository?

#3

Hi,
the best course of action would probably be to open a ticket at our issue tracker (projects.theforeman.org) and wait for the updated package to land in the repositories.