unreachable
The task result meaning Ansible could not connect to the host at all, so the module never ran.
In more detail
Typical causes are a host name that does not resolve, a machine that is switched off, a closed SSH port or a login that is refused. Rewriting the task will not help; fix the connection first, using the ping module to test it.
Related terms
- failed — The task result meaning the module ran on the host but could not do what the task asked.
- ping module — The module that connects to a host, starts Python there and replies pong, proving the whole path to the host works.
- connection variables — Inventory variables with reserved names, such as ansible_user, ansible_port and ansible_connection, that tell Ansible how to reach and log in to a host.
- task result — The report a module sends back for each host: a status such as ok, changed, failed, unreachable or skipped, plus data in JSON.
Taught in
- What Configuration Management Is — Ansible Configuration Management at Scale
- Installing Ansible — Ansible Configuration Management at Scale
- Your First Ad Hoc Command — Ansible Configuration Management at Scale
- Connections And Privilege Escalation — Ansible Configuration Management at Scale
- Playbook Syntax And YAML — Ansible Configuration Management at Scale
- Writing Your First Playbook — Ansible Configuration Management at Scale
- Modules And Idempotency — Ansible Configuration Management at Scale
- Check Mode And Diff — Ansible Configuration Management at Scale
- Handlers And Notify — Ansible Configuration Management at Scale
- Handlers And Failure: notify, block, rescue And always — RHCE in Ansible (EX294): Automate Red Hat Systems