Container status check → ignore_errors: true (registers container_status but never asserts on it)
Deployments can silently fail while the playbook reports green. You only find out when a service is unreachable.
Fix
Replace the status check with a real assertion:
- name:Check container statusansible.builtin.shell:docker compose ps --services --filter status=runningargs:chdir:~/dockerregister:running_containerschanged_when:false- name:Fail if any containers are not runningansible.builtin.fail:msg:"Some containers failed to start"when:running_containers.stdout_lines | length == 0
## Problem
Three tasks in a row suppress all errors:
1. `docker compose up -d` → `ignore_errors: true`
2. 30-second pause
3. Container status check → `ignore_errors: true` (registers `container_status` but never asserts on it)
Deployments can silently fail while the playbook reports green. You only find out when a service is unreachable.
## Fix
Replace the status check with a real assertion:
```yaml
- name: Check container status
ansible.builtin.shell: docker compose ps --services --filter status=running
args:
chdir: ~/docker
register: running_containers
changed_when: false
- name: Fail if any containers are not running
ansible.builtin.fail:
msg: "Some containers failed to start"
when: running_containers.stdout_lines | length == 0
```
**Files:** `playbooks/deploy.yml`, `playbooks/disaster.yml`, `playbooks/redeploy.yml`
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
Three tasks in a row suppress all errors:
docker compose up -d→ignore_errors: trueignore_errors: true(registerscontainer_statusbut never asserts on it)Deployments can silently fail while the playbook reports green. You only find out when a service is unreachable.
Fix
Replace the status check with a real assertion:
Files:
playbooks/deploy.yml,playbooks/disaster.yml,playbooks/redeploy.yml