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
ansible-test fails to check 'requires_ansible' field in meta/runtime.yml of collection #75353
Comments
@mattclay please take a look |
I think you need to pass ansible/lib/ansible/plugins/loader.py Lines 32 to 39 in 865bda3
|
@felixfontein unfortunately it doesn't help, still missing |
I think this should be as easy as adding |
Fix ansible#75353 After requires_ansible field was added as mandatory to runtime.yml file, ansible-test fails to check this field if it doesn't have packaging module. [1] ansible/galaxy-importer#124
if this is it, I prepared #75356 |
* Add packaging to requirement of ansible-test Fix #75353 After requires_ansible field was added as mandatory to runtime.yml file, ansible-test fails to check this field if it doesn't have packaging module. [1] ansible/galaxy-importer#124
…5356) * Add packaging to requirement of ansible-test Fix ansible#75353 After requires_ansible field was added as mandatory to runtime.yml file, ansible-test fails to check this field if it doesn't have packaging module. [1] ansible/galaxy-importer#124 (cherry picked from commit 40ca87a) Co-authored-by: Sergey <sshnaidm@users.noreply.github.com>
Disable ansible-test since it's broken in 2.11[1] [1] ansible/ansible#75353 Change-Id: Idd2f99ddfe507b5b02de206c1f8c75692d6a84a2
* Add packaging to requirement of ansible-test Fix #75353 After requires_ansible field was added as mandatory to runtime.yml file, ansible-test fails to check this field if it doesn't have packaging module. [1] ansible/galaxy-importer#124 (cherry picked from commit 40ca87a) Co-authored-by: Sergey <sshnaidm@users.noreply.github.com>
Add the meta/runtime.yml to appease galaxy imports. See ansible-collections/overview#45 <quote> Ansible Galaxy unexpectedly made a change to require mandatory requires_ansible in meta/runtime.yml file for uploading collection[1][2]. And after you add it you'll probably will hit ansible-test failure in sanity checks if you use it with --venv option, since it can't check this field because of failing requirement[3]. Worth to mention you must have meta/runtime.yml now for your collection to be uploaded. [1] ansible/galaxy-importer#122 [2] ansible/galaxy-importer#124 [3] ansible/ansible#75353 </quote>
Add the meta/runtime.yml to appease galaxy imports. See ansible-collections/overview#45 <quote> Ansible Galaxy unexpectedly made a change to require mandatory requires_ansible in meta/runtime.yml file for uploading collection[1][2]. And after you add it you'll probably will hit ansible-test failure in sanity checks if you use it with --venv option, since it can't check this field because of failing requirement[3]. Worth to mention you must have meta/runtime.yml now for your collection to be uploaded. [1] ansible/galaxy-importer#122 [2] ansible/galaxy-importer#124 [3] ansible/ansible#75353 </quote>
Summary
Because Ansible Galaxy requires now to have
requires_ansible
field[1][2] inmeta/runtime.yml
file, when adding it and runningansible-test
with--venv
option, it fails (requiringpackaging
module):[1] ansible/galaxy-importer#122
[2] ansible/galaxy-importer#124
Issue Type
Bug Report
Component Name
ansible-test
Ansible Version
Configuration
$ ansible-config dump --only-changed
OS / Environment
any
Steps to Reproduce
Expected Results
ansible-test to run without failing on missing requirements with
--venv
optionActual Results
ansible-test fails
Code of Conduct
The text was updated successfully, but these errors were encountered: