Runtime Configuration
147 incident problems about Runtime Configuration. Start with the reviewed ones.
먼저 읽을 가이드
추천 문제
All problems (147)
LINUX-1390A package mirror health check stays green and unattended upgrades failA package mirror health check stays green and unattended upgrades fail focuses on runtime-configuration and asks the reader to isolate the key signal in Linux. Reachability and trust are separate; package metadata can be accessi...LinuxAdvanced13 minProSECURITY-1307An OIDC mobile deep link works in test and fails in productionA mobile auth flow works in staging and later fails only in production after app-registration values were copied manually.SecurityIntermediate13 minProLINUX-1354An Ubuntu cloud instance keeps restoring an old routeA host seems repaired after a live network fix and later reverts to the broken route after reboot or reprovision events.LinuxAdvanced13 minProK8S-1394A cert-manager HTTP01 solver pod comes up and challenges still failA cert-manager HTTP01 solver pod comes up and challenges still fail focuses on Identity And Access and asks the reader to isolate the key signal in Kubernetes. Challenge traffic may reach a different address family than the one o...KubernetesAdvanced14 minProLINUX-1382A cloud-init host boots cleanly and one app misses its secretsA cloud-init host boots cleanly and one app misses its secrets focuses on cluster-maintenance and asks the reader to isolate the key signal in ubuntu. One-time bootstrap failures often come from stage ordering and restarted dependencies,...LinuxAdvanced14 minProLINUX-1317A Docker bind mount looks correct and file permissions still failA Docker bind mount looks correct and file permissions still fail focuses on Identity And Access and asks the reader to isolate the key signal in Linux. Permission errors after launcher changes can be label drift, not Unix mode dr...LinuxIntermediate14 minProLINUX-1332A Fedora host joins the network and never gets production trafficA Fedora host joins the network and never gets production traffic focuses on network-segmentation and asks the reader to isolate the key signal in Linux. Stable interface names are part of the automation contract, and stale pr...LinuxAdvanced14 minProLINUX-1342A Fedora host reboots cleanly and Podman networking breaksA host update leaves containerized services online but unreachable after reboot when the networking device naming changed under Podman.LinuxAdvanced14 minProLINUX-1364A Fedora host updates cleanly and containerized DNS failsA Fedora host updates cleanly and containerized DNS fails focuses on dns-resolution and asks the reader to isolate the key signal in Linux. Split-DNS failures often come from stale link association inside the resolver, not from ba...LinuxAdvanced14 minProLINUX-1348A log shipping agent restarts foreverA host monitoring agent upgrade seems routine and later the service starts crash-looping despite a valid configuration and reachable backend.LinuxAdvanced14 minProLINUX-1379A mount unit reports success at boot and the application still sees an empty...A mount unit reports success at boot and the application still sees an... focuses on runtime-configuration and asks the reader to isolate the key signal in Linux. A green mount unit can still be wrong if it raced the network path behind the mount...LinuxAdvanced14 minProLINUX-1394A network-online target is reached and one VPN-dependent service still failsA network-online target is reached and one VPN-dependent service still fails focuses on network-segmentation and asks the reader to isolate the key signal in Linux. Network-online means very little for services that depend on specific rout...LinuxAdvanced14 minProLINUX-1352A Podman rootless service survives reboot and loses egressA Podman rootless service survives reboot and loses egress focuses on network-segmentation and asks the reader to isolate the key signal in Linux. Post-reboot networking issues often stem from host profile drift rather t...LinuxAdvanced14 minProLINUX-1368A rootless Podman service reports healthy and the first outbound call failsA rootless Podman service reports healthy and the first outbound call fails focuses on firewall-policy-basics and asks the reader to isolate the key signal in Linux. Reload-safe firewall state matters more when user-namespace-specific rule...LinuxAdvanced14 minProLINUX-1384A sudo policy looks correct and one automation user loses accessA sudo policy looks correct and one automation user loses access focuses on Identity And Access and asks the reader to isolate the key signal in Linux. Sudo regressions often come from tag precedence and include ordering, not from the presen...LinuxAdvanced14 minProK8S-1290A Job runs successfully once and then flakesA batch process or long-running job reads a mounted secret once and later begins failing after an external rotation event.KubernetesIntermediate15 minProK8S-1278A pod can reach services by IP but not by nameA monitoring or system pod using hostNetwork starts failing service discovery even though raw IP connectivity is fine.KubernetesIntermediate15 minProLINUX-1280A reverse proxy only breaks one websocket clientOne websocket-based UI or client drops repeatedly while ordinary web traffic and even other chatty websocket clients look fine.LinuxIntermediate15 minProK8S-1284An ALB ingress rule looks correct but one path returns 404A working ingress is migrated to a newer API version and only one nested route stops matching even though the rule appears equivalent.KubernetesIntermediate15 minProLINUX-1284A bind-mounted configuration directory looks correct but one file keeps...A bind-mounted configuration directory looks correct but one file keeps... focuses on filesystem-hygiene and asks the reader to isolate the key signal. Bind mounts hide the underlay at runtime, not necessarily every package script's assumpt...LinuxAdvanced16 minPro