Foreman 3.1 on CentOS 8 stream - new Ansible issue?

Problem:
Ansible jobs on Foreman 3.1 with ansible plugin are now failing on CentOS stream 8 since CentOS stream 8 added ansible 2.12

Expected outcome:
Ansible jobs continue to run.

Foreman and Proxy versions:

rubygem-smart_proxy_dynflow_core-0.4.1-1.fm2_6.el8.noarch
rubygem-smart_proxy_reports-0.0.5-1.fm3_1.el8.noarch
rubygem-smart_proxy_ansible-3.3.0-1.fm3_1.el8.noarch
rubygem-smart_proxy_pulp-3.2.0-2.fm3_1.el8.noarch
rubygem-smart_proxy_remote_execution_ssh-0.5.1-2.fm3_1.el8.noarch
rubygem-smart_proxy_dynflow-0.6.1-2.fm3_1.el8.noarch

Distribution and version: CentOS 8 stream, current

Other relevant data:

This error is now occuring in my job logs:

   2:
to new standard, use callbacks_enabled instead. This feature will be removed 
   3:
from ansible-core in version 2.15. Deprecation warnings can be disabled by 
   4:
setting deprecation_warnings=False in ansible.cfg.
   5:
ERROR! Unexpected Exception, this is probably a bug: No module named 'psutil'
   6:
to see the full traceback, use -vvv
   7:
Exit status: 250```

Based on https://github.com/ansible/ansible-runner/issues/54 and the fact that there is currently not a python38-psutils package available in CentOS 8 stream, I'm attributing this error to that.  I currently plan to mask the ansible 2.12 packages in Stream and go back to the ConfigManagement SIG packaging of Ansible.