-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
homebrew module: task fails on warning message #7044
Comments
Files identified in the description: If these files are incorrect, please update the |
!component =plugins/modules/homebrew.py |
Files identified in the description: If these files are incorrect, please update the |
I was just having the same issue with |
Is this fixed or any other workarounds? I am having the same issue with Avoiding with |
We see a similar failure mode when the intention is to install a formula.
What's the recommended approach here? |
@HarryWeppner seeing the same issue. Tried adding |
I encounter this same problem, and it seems to be caused by packages that are also available as casks (like awscli, httpie, etc.). I specified the As a workaround I resolved this locally by doing the following:
|
It is a breaking change for anyone who is using this module for casks, though in my mind absolutely worth it. Even using Homebrew CLI directly this duality has been an issue for me. |
Yeah, that's the issue with the commit: fa30b02#diff-109efc689f4332320bad76472328471ef85a0faeae32ec97086c9790e244c69eR491-R494 ^^ @thewalla07 where we start checking error messages (stderr) of the @edv, I would love if you could create a PR for the fix. Do not want to take your credits )) |
Instead of checking if there is an error message, which can also be a warning, we now check the return code. This commint fixes ansible-collections#8229 ansible-collections#7044
Instead of checking if there is an error message, which can also be a warning, we now check the return code. This commit fixes ansible-collections#8229 ansible-collections#7044
Instead of checking if there is an error message, which can also be a warning, we now check the return code. This commit fixes ansible-collections#8229 ansible-collections#7044
I added a simple fix for this issue in #8406 |
Instead of checking if there is an error message, which can also be a warning, we now check the return code. This commit fixes ansible-collections#8229 ansible-collections#7044
Instead of checking if there is an error message, which can also be a warning, we now check the return code. This commit fixes ansible-collections#8229 ansible-collections#7044
Instead of checking if there is an error message, which can also be a warning, we now check the return code. This commit fixes ansible-collections#8229 ansible-collections#7044
Instead of checking if there is an error message, which can also be a warning, we now check the return code. This commit fixes ansible-collections#8229 ansible-collections#7044
Instead of checking if there is an error message, which can also be a warning, we now check the return code. This commit fixes ansible-collections#8229 ansible-collections#7044
Instead of checking if there is an error message, which can also be a warning, we now check the return code. This commit fixes #8229 #7044 Co-authored-by: Strahinja Kustudic <[email protected]>
Instead of checking if there is an error message, which can also be a warning, we now check the return code. This commit fixes #8229 #7044 Co-authored-by: Strahinja Kustudic <[email protected]> (cherry picked from commit 43cb5a0)
…g because of warnings (#8425) Fix the homebrew module failing because of warnings (#8406) Instead of checking if there is an error message, which can also be a warning, we now check the return code. This commit fixes #8229 #7044 Co-authored-by: Strahinja Kustudic <[email protected]> (cherry picked from commit 43cb5a0) Co-authored-by: Strahinja Kustudic <[email protected]>
…ons#8406) Instead of checking if there is an error message, which can also be a warning, we now check the return code. This commit fixes ansible-collections#8229 ansible-collections#7044 Co-authored-by: Strahinja Kustudic <[email protected]> (cherry picked from commit 43cb5a0)
#8429) Fix the homebrew module failing because of warnings (#8406) Instead of checking if there is an error message, which can also be a warning, we now check the return code. This commit fixes #8229 #7044 Co-authored-by: Strahinja Kustudic <[email protected]> (cherry picked from commit 43cb5a0) Co-authored-by: Strahinja Kustudic <[email protected]>
…ons#8406) Instead of checking if there is an error message, which can also be a warning, we now check the return code. This commit fixes ansible-collections#8229 ansible-collections#7044 Co-authored-by: Strahinja Kustudic <[email protected]>
Summary
Given this Ansible task:
If one of the packages is already the latest version, execution is stopped and the tasks fails:
I expect this to be a non-fatal warning, and that it continues running the playbook.
Issue Type
Bug Report
Component Name
homebrew
Ansible Version
Community.general Version
Configuration
OS / Environment
Debian 12
Steps to Reproduce
Expected Results
When one of the packages is already up to date, it continues upgrading the other packages and this tasks succeeds.
Actual Results
Execution stops at this point.
Code of Conduct
The text was updated successfully, but these errors were encountered: