In the Ansible Automation Platform, jobs fail with "ERROR! couldn't resolve" despite the necessary collections being synced on the Private Automation Hub.

Solution Verified - Updated -

Issue

  • In the Ansible Automation Platform, jobs fail with "ERROR! couldn't resolve" despite the necessary collections being synced on the Private Automation Hub.
  • The customer is using the modules of the collection in their playbooks. They are using our default execution environment and at runtime the controller error says it can't resolve that module name. The module name is correct, the collection is available in PAH and other customers are able to use the module in their playbooks.

    Parsed /runner/inventory/hosts inventory source with script plugin
    ERROR! couldn't resolve module/action 'zos_data_set'. This often indicates a misspelling, missing collection, or incorrect module path.
    The error appears to be in '/runner/project/playbooks/ibmtest.yml': line 10, column 5, but may be elsewhere in the file depending on the exact syntax problem.
    

Environment

  • Red Hat Ansible Automation Platform 2.4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content