⚡ ~/naveed Interview Prep
⚡ Portfolio Home 👤 About Naveed Bio & Credentials 📫 Contact Naveed Get In Touch ✍️ Engineering Blog Deep Dives 🎯 Interview Hub 1,000+ Scenarios ☸️ Kubernetes Mastery Hub 24 Modules 🎮 DevOps Arcade & Quizzes Subnet Blitz ⚡ 🗺️ DevOps Roadmaps PDFs & Guides 🤖 Morpheus Analysis AI Quant ↗ 🛠️ Developer Tools Utilities 🧪 Labs & Experiments 📄 Interactive CV & Certs 🔗 All Links & Socials ⚡ Join The Dispatch (Weekly SRE Newsletter) →
← Back to All Linux & SRE Interview Questions Scenario 112 of 135 in Linux & SRE
Staff SRE / Principal Architect [L3] Linux System Reliability & Operations Staff SRE Scenario [L3]

Q: You need to perform a kernel upgrade on a production server with zero unplanned downtime. The server runs on RHEL/CentOS. Describe the safest approach.

Kernel upgrades inherently require a reboot on standard Linux (unlike kpatch/livepatch for security fixes). The goal is to minimize risk and ensure rollback capability.

#Linux #L3 #SRE #Systems #Troubleshooting
🎙️ Candidate Opening & Architectural Context
""Never reboot a server blindly; always capture top process telemetry, lsof descriptors, and thread dumps first. The interviewer is testing: Kernel lifecycle management, risk mitigation, rollback strategy.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third.""
Advertisement
⚡ Recommended Practice Lab

Want to master this scenario in a live sandbox? The Linux Foundation's Certified System Administrator (LFCS) & SRE Track covers this exact problem with hands-on terminal drills.

🛠️ Production Runbook & Step-by-Step Resolution

Direct Answer: "Never reboot a server blindly; always capture top process telemetry, lsof descriptors, and thread dumps first. The interviewer is testing: Kernel lifecycle management, risk mitigation, rollback strategy.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."

1️⃣

Initial Diagnostics & Root Cause Analysis

Kernel upgrades inherently require a reboot on standard Linux (unlike kpatch/livepatch for security fixes). The goal is to minimize risk and ensure rollback capability.

  • Pre-flight checks:
  • Verify current kernel: uname -r
  • Check available updates: yum list kernel
  • Review changelog for breaking changes: yum updateinfo info kernel
  • Ensure GRUB has the old kernel as fallback
  • Install (don't update) the new kernel:
  • Verify boot configuration:
2️⃣

Remediation & Permanent Safeguards

Safe upgrade workflow: This installs alongside the old kernel rather than replacing it.

yum install kernel-5.14.0-362.el9
  • Schedule maintenance window:
  • Drain traffic from the server (remove from load balancer).
  • Reboot into the new kernel.
  • Run validation tests (application health checks, network connectivity, disk mounts).
  • Rollback plan (if issues arise):
  • Post-validation: Keep the old kernel installed for at least 2 weeks before removing it with yum remove kernel-.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Pre-flight checks:."
⚡ 60-Second Elevator Pitch Talking Points
  • Pre-flight checks:
  • Verify current kernel: uname -r
  • Check available updates: yum list kernel
⛔ Critical Candidate Mistakes to Avoid in This Scenario

Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:

  1. Issuing immediate kill -9 (SIGKILL) commands rather than allowing graceful termination via kill -15 (SIGTERM) when configuring need perform kernel SIGKILL immediately halts execution without allowing processes to flush memory buffers, commit database transactions, or remove stale PID locks.
  2. Overlooking file system inode exhaustion (df -i) when diagnosing 'No space left on device' errors when configuring need perform kernel Millions of small files or unrotated session tokens can exhaust available file system inodes even when standard disk storage (df -h) shows ample free space.
  3. Exhausting open file descriptor allocations (ulimit -n) under intensive concurrent socket connections when configuring need perform kernel Reaching file descriptor exhaustion throws 'Too many open files' errors, preventing services from accepting new TCP client socket connections.
  4. Permitting defunct zombie processes to accumulate without fixing parent process SIGCHLD waitpid reaping when configuring need perform kernel Zombie processes consume process table entries; accumulating zombies can exhaust the system maximum PID limit (pid_max).
Advertisement
Want more Linux & SRE scenarios?
Explore our complete collection of scenario-based Linux & SRE interview runbooks.
Browse All Linux & SRE Questions →