Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

project_update.yml keeps on skipping taks despite changed requirements.yml #10058

Closed
Bishwash-Pokhrel opened this issue Apr 30, 2021 · 2 comments
Labels

Comments

@Bishwash-Pokhrel
Copy link

Bishwash-Pokhrel commented Apr 30, 2021

ISSUE TYPE
  • Bug Report
SUMMARY
ENVIRONMENT
  • AWX version: 19.0.0
  • AWX install method: minikube/docker on linux
  • Ansible version: 2.9.13
  • Operating System: Linux
  • Web Browser: Chrome
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.
screenshot3
screenshot2

@Bishwash-Pokhrel 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
@shanemcd
Copy link
Member

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)

@Bishwash-Pokhrel
Copy link
Author

Bishwash-Pokhrel commented May 4, 2021

Hi, Even after following the steps from the comment. The job is still skipping. Here is what I did:

  1. Created a new galaxy credential from /api/v2/credentials/?credential_type__kind=galaxy.
  2. 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-issue

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants