{"id":2362,"date":"2026-11-20T12:50:00","date_gmt":"2026-11-20T12:50:00","guid":{"rendered":"https:\/\/devopsschool.org\/blog\/eight-devops-problems-five-whys\/"},"modified":"2026-11-20T12:50:00","modified_gmt":"2026-11-20T12:50:00","slug":"eight-devops-problems-five-whys","status":"publish","type":"post","link":"https:\/\/devopsschool.org\/blog\/eight-devops-problems-five-whys\/","title":{"rendered":"8 Everyday DevOps Problems That Reveal Their Cause After Five Whys"},"content":{"rendered":"<p>Early in a DevOps career, you collect a pile of small mysteries: the build that fails on Mondays, the container that works on one laptop only, the pipeline that goes red for no reason anyone can name. Learners often fix each one and move on, then meet the same mystery again in new clothes. Asking why five times is the habit that turns a heap of anecdotes into understanding. Here are eight everyday problems, each with a short chain showing where it tends to end, written the way a mentor might sketch them on a napkin.<\/p>\n<p>A short story shows why this matters. A learner I once taught spent an entire evening fixing a failing job by trial and error, and felt proud when it turned green. The following week the same job failed again, and the same evening was spent again. Only when a study partner kept saying &#8220;but why did it fail?&#8221; did the learner notice that the evening&#8217;s fix had touched a symptom each time. After that, the learner kept a notebook, and the evenings got shorter.<\/p>\n<h2>1. The build that fails only on Mondays<\/h2>\n<p>Why does it fail? A dependency cannot be downloaded. Why not? The mirror it points to is unreachable early in the week. Why that mirror? The configuration was copied from an old project. Why copied? New projects start from whatever an earlier project looks like. Why? There is no maintained starter configuration. The lesson: the build is not flaky; the starting point is unowned, and every new project inherits that gap along with the configuration.<\/p>\n<h2>2. The container that runs on one machine only<\/h2>\n<p>Why does it fail elsewhere? A library version differs. Why differ? The image installs the latest release at build time. Why unpinned? Nobody wrote down which versions the application was tested against. Why not? The team never defined what &#8220;tested&#8221; means for an image. Why? The first version was a quick experiment that stayed in use. The lesson: experiments need a retirement or promotion date.<\/p>\n<h2>3. The deployment that needs one specific person<\/h2>\n<p>Why can only one person deploy? The steps live in their head. Why? They built the process alone. Why alone? It was urgent at the time. Why was it never shared? Nobody scheduled time to document it. Why? Documentation is treated as extra work rather than as part of the task. The lesson: a task is not finished until another person can repeat it. Learners interested in sharpening this kind of thinking will find more in <a href=\"https:\/\/devopsschool.org\/blog\/devops-problem-solving-how-to-build-critical-thinking-skills\/\">the piece about growing your critical thinking when solving DevOps puzzles<\/a>.<\/p>\n<h2>4. The test suite everyone has stopped trusting<\/h2>\n<p>Why is it ignored? It fails often without real defects. Why does it fail without defects? Some tests depend on timing. Why did timing-based tests get written? They were the quickest way to check asynchronous behaviour. Why was quick chosen? There was pressure to ship and no agreed standard for test quality. Why no standard? Test code is not reviewed as strictly as application code. The lesson: apply the same review habits to tests.<\/p>\n<h2>5. The alert that wakes the team every week<\/h2>\n<p>Why does it fire? A disk fills past a threshold. Why does the disk fill? Log files are never rotated. Why not rotated? The default configuration was left alone. Why left alone? Nobody reviews defaults after installation. Why? Setup is seen as a one-time job. The lesson: installation is the beginning of operations, not the end.<\/p>\n<h2>6. The pipeline that takes forty minutes<\/h2>\n<p>Why so slow? Every stage runs in sequence. Why sequence? The pipeline grew one step at a time. Why does that matter? Nobody looked at the whole shape. Why not? Each addition seemed small. Why was nobody watching the total? Pipeline duration is not tracked or discussed. The lesson: what nobody measures quietly gets worse.<\/p>\n<h2>7. The secret that ended up in the wrong place<\/h2>\n<p>Why was it exposed? A configuration file with a credential was committed. Why committed? It was easier than setting up the proper store. Why was the proper store hard? The instructions were out of date. Why out of date? Whoever wrote them moved teams. Why did nothing change? Ownership of the instructions moved with no one. The lesson: documentation needs an owner who survives reorganisations.<\/p>\n<h2>8. The environment that differs from production<\/h2>\n<p>Why did a bug appear only in production? A setting differs from staging. Why does it differ? Staging was built by hand. Why by hand? The automation covered production only. Why only production? It was prioritised after an earlier outage. Why was staging left behind? The follow-up task was never scheduled. The lesson: after any incident, finish the second half of the fix. A related look at skills learners often lack is in <a href=\"https:\/\/devopsschool.org\/blog\/devops-knowledge-gaps-students-must-fill-a-practical-guide\/\">this practical guide to the gaps students should close<\/a>.<\/p>\n<h2>The pattern across all eight<\/h2>\n<p>Read the final answers again. Almost none of them concerns a tool. They concern ownership, review, documentation, scheduling and measurement. That is typical: the early answers sit in technology and the late ones sit in how people agree to work. You can test this on your own history. Take any three incidents you have fixed this year, write their chains, and underline the last answer in each. If two of the three underlines say something like &#8220;nobody owned it&#8221; or &#8220;nobody reviewed it,&#8221; you have found a habit worth fixing before you add one more tool to the stack. For a learner, that is good news, because habits are the part you can change this week, and employers value people who notice them.<\/p>\n<h2>A note on how learners find reference material<\/h2>\n<p>When you build your own notes, it helps to see how different websites file their material. One example worth glancing at is <a href=\"https:\/\/bestorthohospitals.com\/\">a travel-for-treatment directory site that lists orthopaedic hospitals and doctors next to articles, a discussion forum and procedure pages, plus a country and keyword search<\/a>. It is an off-topic example only; its own statements are not repeated here. The takeaway is purely organisational: separate shelves for separate kinds of question.<\/p>\n<h2>How to practise on your own<\/h2>\n<p>Keep a notebook with five columns: the problem, the whys, the process-level cause, the change you tried, and what happened. Try one chain a week on a real annoyance from your lab, course project or job. Say each answer aloud to a study partner and let them ask why once more. After two months you will have a small library of chains, and you will see the same final answers recurring, which is the beginning of real operational judgment. Share the notebook with a mentor or a study group occasionally, because a fresh reader will often spot the level where you stopped.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Eight common DevOps headaches, from Monday build failures to untrusted tests, each traced with a short chain of whys to the process-level cause behind it.<\/p>\n","protected":false},"author":5,"featured_media":2363,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[489],"tags":[],"class_list":["post-2362","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops-careers"],"_links":{"self":[{"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/posts\/2362","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/comments?post=2362"}],"version-history":[{"count":0,"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/posts\/2362\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/media\/2363"}],"wp:attachment":[{"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/media?parent=2362"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/categories?post=2362"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/tags?post=2362"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}