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

Error in meta_dependency_check with AAP 2.5 using ansible.controller and collection version 2.11.0 #983

Closed
bogdanmuresan opened this issue Nov 21, 2024 · 1 comment
Labels
invalid This doesn't seem right wontfix This will not be worked on

Comments

@bogdanmuresan
Copy link
Contributor

bogdanmuresan commented Nov 21, 2024

Summary

Job fails with:

TASK [infra.controller_configuration.meta_dependency_check : Ensure one is installed] ***  
fatal: [localhost]: FAILED! => {"changed": false, "msg": "One of awx.awx or ansible.controller must be installed"}

Because:

changed: false
stdout: ''
stderr: "\e[0;35m[DEPRECATION WARNING]: ANSIBLE_COLLECTIONS_PATHS option, does not fit var \e[0m\n\e[0;35mnaming standard, use the singular form ANSIBLE_COLLECTIONS_PATH instead. This \e[0m\n\e[0;35mfeature will be removed from ansible-core in version 2.19. Deprecation warnings\e[0m\n\e[0;35m can be disabled by setting deprecation_warnings=False in ansible.cfg.\e[0m\n\e[0;31mERROR! Error when getting collection version metadata for ansible.controller:4.6.2 from default (https://galaxy.ansible.com/api/) (HTTP Code: 404, Message: Not found. Code: not_found)\e[0m"
rc: 1
cmd:
  - ansible-galaxy
  - collection
  - verify
  - ansible.controller
start: '2024-11-21 09:42:15.078312'
end: '2024-11-21 09:42:17.008850'
delta: '0:00:01.930538'
msg: non-zero return code
invocation:
  module_args:
    _raw_params: ansible-galaxy collection verify ansible.controller
    _uses_shell: false
    expand_argument_vars: true
    stdin_add_newline: true
    strip_empty_ends: true
    argv: null
    chdir: null
    executable: null
    creates: null
    removes: null
    stdin: null
stdout_lines: []
stderr_lines:
  - "\e[0;35m[DEPRECATION WARNING]: ANSIBLE_COLLECTIONS_PATHS option, does not fit var \e[0m"
  - "\e[0;35mnaming standard, use the singular form ANSIBLE_COLLECTIONS_PATH instead. This \e[0m"
  - "\e[0;35mfeature will be removed from ansible-core in version 2.19. Deprecation warnings\e[0m"
  - "\e[0;35m can be disabled by setting deprecation_warnings=False in ansible.cfg.\e[0m"
  - "\e[0;31mERROR! Error when getting collection version metadata for ansible.controller:4.6.2 from default (https://galaxy.ansible.com/api/) (HTTP Code: 404, Message: Not found. Code: not_found)\e[0m"
_ansible_no_log: false
failed_when_result: false

I am not sure why it looks for the ansible.controller collection on galaxy, but shouldn't the check use the offline mode?
https://github.com/redhat-cop/infra.aap_configuration/blob/devel/roles/meta_dependency_check/tasks/main.yml#L21

ansible-galaxy collection verify ansible.controller --offline

Or am I doing something wrong? I
Workaround for now is to set controller_dependency_check: false

Later edit: I see this has been fixed in 3.0.0 by setting controller_dependency_check to false.
Still, I leave this here, as I think the proper fix is to use the offline argument with ansible-galaxy

Issue Type

  • Bug Report
@bogdanmuresan bogdanmuresan added bug Something isn't working new New issue, this should be removed once reviewed labels Nov 21, 2024
@bogdanmuresan bogdanmuresan changed the title Error in meta_dependency_check with AAP 2.5 using ansible.controller and collection version 2.10.0 Error in meta_dependency_check with AAP 2.5 using ansible.controller and collection version 2.11.0 Nov 21, 2024
@djdanielsson
Copy link
Collaborator

djdanielsson commented Nov 21, 2024

We are not supporting(fixing any issues) 2.5 with controller_configurtion is not written to work with 2.5. Migrate to aap_configuration if you want to do config as code for AAP 2.5.

@djdanielsson djdanielsson added invalid This doesn't seem right wontfix This will not be worked on and removed bug Something isn't working new New issue, this should be removed once reviewed labels Nov 21, 2024
@djdanielsson djdanielsson closed this as not planned Won't fix, can't repro, duplicate, stale Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid This doesn't seem right wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants