When Your Infrastructure is a Buggy Program: Understanding Faults in Infrastructure as(…)
summary
360 bugs across Ansible Puppet Chef registries are analyzed and classified into six symptom groups (most commonly external configuration failures), ten root causes (top are system interaction and compatibility), and concrete reproduction requirements. About 25% are OS-sensitive and roughly half require specific system state versus just input. Fixes are usually small (few files/lines), suggesting automated repair is promising. The dataset and artifacts are available for reproduction and further tooling work.
AI-written summary · about
chapters (8)
- 0:00Infrastructure as code bugs
- 3:09Why IaC bugs matter
- 8:33Infrastructure bug symptoms
- 9:18Root causes of IaC failures
- 11:26OS sensitivity in bugs
- 12:29State dependencies in bugs
- 14:41Fixing IaC bugs and tool gaps
- 16:27Q&A
related talks
52mEscaping Developer Nightmares
27mCatch Me If You Can: Hunting Misconfigurations Before They...
40mHow to Identify and Avoid Cracks and Bumps in your Digital Infrastructure? By Consi...
18mActor Concurrency Bugs: A Comprehensive Study on Symptoms, Root Causes, API Usages, and Differences
33mFamiliar Smells I’ve Detected in Your Systems Engineering Organization and How to Fix Them
29mMake It Fixable: Preparing for Security Vulnerability Reports
36mWhy programming is fiendishly difficult and what we can do about it
55mArchitecture Blindspots, Biases, and Blunders: Avoiding Common Pitfalls in System Design