Ansible Skipped daemon-reload and systemd Used the Old Unit — Ansible Package & Service Modules
на канале: TheCodeForge
The `service` module doesn't run `systemctl daemon-reload`, so after a unit file update systemd used the cached old version and the service failed with 'Unit not found'. This is package and service management done right: apt/yum/dnf, the service/systemd modules, daemon_reload, enabled vs started, and ordering updates so systemd sees your changes.
⏳ Timestamps:
0:00 - Cold open: Failed to start myapp.service: Unit not found
0:11 - Intro
0:18 - What Is This?
0:35 - Package Module Basics
0:55 - Apt Module Specifics
1:15 - Yum and Dnf Modules
1:32 - Pip Module Basics
1:49 - Service Module Legacy
2:09 - Systemd Module Full Control
2:29 - Failed to start myapp.service: Unit not found
2:49 - The Fix
3:03 - ⚠ Gotcha: Using service module on systemd systems
3:15 - ⚠ Gotcha: Using state: restarted without enabled
3:27 - ⚠ Gotcha: Forgetting update_cache with package module
3:39 - ⚠ Gotcha: Downgrading without allow_downgrade
3:48 - ⚠ Gotcha: Using state: latest in production
3:56 - Managing Multiple Services
4:15 - State vs Enabled
4:31 - Daemon Reload Best Practice
4:49 - Cross-Distro Patterns
5:07 - Using Handlers for Daemon-Reload
5:20 - Version Compatibility: Ansible 2.10+
5:40 - Production Caveat: Idempotency with Pip
5:55 - Debugging Guide
6:06 - Interview Questions
6:24 - FAQ
6:41 - Key Takeaways
6:54 - Next up
7:06 - Wrap-up
👉 Full article + code: https://thecodeforge.io/devops/ansibl...
⏭ Next up: Ansible Command and Shell Modules