ansible · ansible/2
2
One or more hosts failed
The playbook ran to completion but at least one task returned a failure status on at least one host. The specific failing tasks and hosts are listed in the play recap.
Also defined in
- bazel Command Line Problem A command-line usage error: bad or illegal flags, an unrecognized command, or an invalid environment variable. No build was attempted.
- composer Dependency Resolution Error The dependency solver could not find a consistent set of package versions satisfying all constraints in composer.json. The output lists the conflicting requirements. Relaxing version constraints, running `composer update`, or removing conflicting packages resolves this.
- curl Failed to initialise curl failed to initialise. This is very rare.
- eslint Linting Failed (Configuration or Internal Error) ESLint could not run due to a configuration problem (missing config file, invalid rule options, unparseable source file) or an internal error. Check the ESLint config and ensure all plugins and parsers are installed.
- git Usage or configuration error The command was invoked incorrectly, or a configuration error was detected. Often accompanies a usage message.
- gradle Task Not Found The Gradle task specified on the command line does not exist in the build script. Verify the task name with `gradle tasks` and check for typos or missing plugin applications.
- ldap protocolError The server received data that is not well-formed or that violates the LDAP protocol specification. This includes malformed PDUs and unsupported protocol versions.
- make Make Internal Error Make itself encountered a fatal error: an unrecognised command-line option, a syntax error in the Makefile, or another internal problem that prevented the build from starting. This exit code is distinct from a recipe failure (exit code 1).
- modbus ILLEGAL_DATA_ADDRESS The data address referenced in the request is not available on the server. This typically means the combination of reference number and transfer length is invalid.
- mongodb BadValue A command parameter has an invalid value — wrong type, out of range, or not permitted in this context.
- pytest Interrupted Test execution was interrupted before completion — typically by Ctrl+C or a SIGINT signal, or by a plugin calling `pytest.exit()`. Any results collected before the interruption are still reported.
- rsync Protocol incompatibility The local and remote rsync versions are not compatible.
- shell Misuse of shell built-in Incorrect usage of a shell built-in command, such as missing or invalid arguments.
- vue Error in watcher getter An unhandled exception was thrown in the getter function of a watch() or watchEffect() call. The getter is the first argument (the source expression) and runs synchronously to collect dependencies.