-
Bug
-
Resolution: Done-Errata
-
Blocker
-
MTC 1.7.19
-
None
-
None
-
False
-
-
False
-
ToDo
-
-
When installing MTC 1.7.19 from OperatorHub, the migration-operator pod fails during startup. The logs indicate that the Ansible Runner is crashing due to an unhandled KeyError: 'http+unix'. As a result, the installation is stuck in an incomplete state and required controller pods are never deployed. This renders the operator non-functional.
The issue appears to be related to how ansible_runner_http handles status callbacks involving the http+unix scheme, which is not recognized by urllib3 and lacks a corresponding handler in key_fn_by_scheme.
Steps to Reproduce:
- Navigate to OperatorHub in the OpenShift console.
- Attempt to install MTC 1.7.19
- If pre-installed, monitor the status of the MTC installation using:
$oc get all -n openshift-migration
Actual results:
- migration-operator pod crashes in a loop.
- Operator installation remains incomplete and non-functional.
- From the migration operator logs:
Traceback (most recent call last): ... File "/usr/lib/python3.6/site-packages/urllib3/poolmanager.py", line 239, in connection_from_context pool_key_constructor = self.key_fn_by_scheme[scheme] KeyError: 'http+unix'error: open /tmp/ansible-operator/runner/migration.openshift.io/.../artifacts/.../stdout: no such file or directory
- is caused by
-
RHEL-88456 ansible operator fails with error with current python-requests
-
- Closed
-
- links to
-
RHBA-2025:145873 Migration Toolkit for Containers (MTC) 1.7.19 security and bug fix update