dell / omnia

An open-source toolkit for deploying and managing high performance clusters for HPC, AI, and data analytics workloads.
https://omnia-doc.readthedocs.io/en/latest/index.html
Apache License 2.0
219 stars 116 forks source link

Ansible collections are not downloaded for manual project in AWX 19.1.0 #341

Closed ptrinesh closed 3 years ago

ptrinesh commented 3 years ago

Describe the bug Getting the below error while executing a playbook from AWX which uses the modules from 3rd party collections {"reason": "couldn't resolve module/action 'dellemc.openmanage.idrac_lifecycle_controller_status_info'. This often indicates a misspelling, missing collection, or incorrect module path.

To Reproduce Steps to reproduce the behavior:

  1. Create the manual project in awx
  2. Run the job template which uses collections

Expected behavior There should be a way to store collections for manual projects

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

Smartphone (please complete the following information):

Additional context Add any other context about the problem here.

ptrinesh commented 3 years ago

Equivalent issue has been raised in awx community 10236

lwilson commented 3 years ago

@ptrinesh do we have a corrective action planned, or is this something we need to track? It appears that the quick fix in the ticket was to insert the deployment's credentials into the user's Galaxy account (see https://github.com/ansible/awx/issues/10236#issuecomment-847238422). However, this doesn't appear to be a particularly elegant or automatable solution.

Suggestions?

ptrinesh commented 3 years ago

@lwilson i have build the custom image for awx-ee by including the collections and deployed in the awx pod and it is working fine as expected.

stale[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

lwilson commented 3 years ago

@ptrinesh did we ever get a resolution/workaround for this?

stale[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.