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

Patch release broke working repo. #2645

Closed
greg-hellings opened this issue Nov 1, 2022 · 2 comments · Fixed by ansible/ansible-compat#180
Closed

Patch release broke working repo. #2645

greg-hellings opened this issue Nov 1, 2022 · 2 comments · Fixed by ansible/ansible-compat#180
Assignees
Labels
bug new Triage required

Comments

@greg-hellings
Copy link
Contributor

Summary

Version 6.8.5 broke code which previously was passing with 6.8.4.

Issue Type
  • Bug Report
OS / ENVIRONMENT

Github Actions Ubuntu runner

STEPS TO REPRODUCE

See this run of dependabot upgrades that resulted in a broken run.

Desired Behavior

Patch-level changes should not break existing code.

Actual Behavior

Patch release broke existing code with confusing error message. Error message states that requirements.txt does not exist, but it does and has existed.

@greg-hellings greg-hellings added bug new Triage required labels Nov 1, 2022
@sverrehu
Copy link
Contributor

sverrehu commented Nov 1, 2022

We see the same. Several messages like this:

ERROR! Unexpected Exception, this is probably a bug: [Errno 2] No such file or directory: 'verify.yml'

for various files and directories that are there. Before each error, there is a warning that was not there in 6.8.4:

[WARNING]: The specified collections path '/root/.cache/ansible-
compat/1809f7/collections' is not part of the configured Ansible collections
paths '/root/.ansible/collections:/usr/share/ansible/collections'. The
installed collection won't be picked up in an Ansible run.

ansible-lint 6.8.5 using ansible 2.13.5

@ssbarnea ssbarnea self-assigned this Nov 1, 2022
ssbarnea added a commit to ssbarnea/ansible-compat that referenced this issue Nov 1, 2022
ssbarnea added a commit to ssbarnea/ansible-compat that referenced this issue Nov 1, 2022
ssbarnea added a commit to ssbarnea/ansible-compat that referenced this issue Nov 1, 2022
@greg-hellings
Copy link
Contributor Author

This behavior is still present in 6.8.6. See here where the error is still appearing. Now it is complaining about defaults instead of requirements.txt.

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

Successfully merging a pull request may close this issue.

3 participants