Replies: 2 comments 4 replies
-
Did you check if this message is displayed on stderr or stdout? If is is on stderr, that is not a bug, if is on stdout, it is a bug. |
Beta Was this translation helpful? Give feedback.
-
It seems to me we should consider failing, or at least provide a stern warning, when installing With versions 6.9 and prior I can run At least in this case, I could redirect 6.8 (tested via # ansible-lint --version
Failed to locate command: [Errno 2] No such file or directory: 'git'
ansible-lint 6.8.7 using ansible 2.14.1 6.9 (tested via # ansible-lint --version
Failed to locate command: [Errno 2] No such file or directory: 'git'
ansible-lint 6.9.1 using ansible 2.14.1
A new release of ansible-lint is available: 6.9.1 → 6.10.2 But now with 6.10, I only get the error message and no 6.10 (tested via # ansible-lint --help
Failed to find runtime dependency 'git' in PATH
/#
# ansible-lint --version
Failed to find runtime dependency 'git' in PATH
/# |
Beta Was this translation helpful? Give feedback.
-
Summary
The issue of 'git' not being automatically excluded has apparently regressed/reocurred, and so -- when the
git
command is not found, an error message is displayed when runningansible-lint --version
.I've just installed ansible-lint v6.10 (in a python:3-slim container) and see this error when running
ansible-lint --version
.A similar / same symptom was previously addressed in #2641 / #2633 (reported for ansible-lint ver 6.8.4).
Issue Type
OS / ENVIRONMENT
Since the prior issue (#2641 in October) related to a "Fix pip version check", I'm including confirmation that a current version of pip is installed and running in this same container.
It seems the same issue is present in ansible-lint v6.9.1 and v6.8.7
STEPS TO REPRODUCE
Desired Behavior
Unexpected / unnecesarry error messages are not shown when
ansible-lint --version
is run.Actual Behavior
Unexpected / unnecesarry error messages are shown when
ansible-lint --version
is run.Beta Was this translation helpful? Give feedback.
All reactions