You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy the playbook from this playbook. Import it as a project. Set up requirements.yml in your repo and also set it up in awx. Run the job. Make changes in the requirement.yml file and try running the job again.
EXPECTED RESULTS
The job should be executed and installed its respective galaxy collections from requirements.yml.
ACTUAL RESULTS
In the task fetch galaxy collections from collections/requirements.(yml/yaml), despite changing the content of requirement.yml in the repository it keeps on skipping the task indicating that no changes were made in the file. Following are the output of the task.
The text was updated successfully, but these errors were encountered:
Bishwash-Pokhrel
changed the title
project_update.yml keeps on skipping taks despite changed requirements.
project_update.yml keeps on skipping taks despite changed requirements.yml
Apr 30, 2021
Hello. I think this is a bug that's been biting several people lately. Basically, you need to create a Galaxy credential and attach that to your organization. We'll look to see about updating / creating some docs around this. For now, see #8341 (comment)
Hi, Even after following the steps from the comment. The job is still skipping. Here is what I did:
Created a new galaxy credential from /api/v2/credentials/?credential_type__kind=galaxy.
POST /api/v2/organizations/1/galaxy_credentials/
{
"id": 2,
"associate": true
}
The output of SELECT * FROM conf_setting WHERE key='PUBLIC_GALAXY_ENABLED'; :
I have attached the screenshot of the output status.
awx=# SELECT * FROM conf_setting WHERE key='PUBLIC_GALAXY_ENABLED';
id | created | modified | key | value | user_id
----+---------+----------+-----+-------+---------
(0 rows)
Output: Same as previous skipping the tasks from requirements.yml.
ISSUE TYPE
SUMMARY
ENVIRONMENT
STEPS TO REPRODUCE
Copy the playbook from this playbook. Import it as a project. Set up requirements.yml in your repo and also set it up in awx. Run the job. Make changes in the requirement.yml file and try running the job again.
EXPECTED RESULTS
The job should be executed and installed its respective galaxy collections from requirements.yml.
ACTUAL RESULTS
In the task fetch galaxy collections from collections/requirements.(yml/yaml), despite changing the content of requirement.yml in the repository it keeps on skipping the task indicating that no changes were made in the file. Following are the output of the task.


The text was updated successfully, but these errors were encountered: