Rollout Stuck
384 incident problems that show up as “Rollout Stuck”.
먼저 읽을 가이드
추천 문제
All problems (384)
LINUX-062Missing bind mount at boot makes rsync --delete clean the host path instead of the volumeThe sync command is valid, but the intended mount point never appeared and the cleanup step now targets the underlying directory on the root filesystem.LinuxAdvanced24 minProK8S-071PodDisruptionBudget and topology spread leave no legal recovery layout after an AZ outageThe workload had enough replicas before the outage, but after one zone disappears the remaining rules make every recovery option violate either spread or disruption guarantees.KubernetesAdvanced24 minProCICD-058Production environment review waits foreverThe environment requires human approval on paper, but tagged releases stall indefinitely because the reviewer and branch rules were designed only for branch-based promotion.CI/CDAdvanced24 minProSECURITY-055EDR quarantine removes the log shipper binary and blinds central visibilityContainment works on the compromised host, but the action also stops telemetry collection and makes the rest of the investigation much harder.SecurityAdvanced25 minProCICD-029Monorepo path filter misses shared library changesMonorepo path filter misses shared library changes is a hands-on troubleshooting drill. Only some services rebuild because the path filter ignores a shared package that affects multiple deployments. GitHub Rollback and Rollout needs to be checked by narrowing scope, recent cha...CI/CDAdvanced26 minProCICD-036CodeDeploy rollback alarm never firesThe blue-green deployment partially shifts traffic, but the rollback condition never triggers because the health alarm watches only the stable target group.CI/CDAdvanced27 minProLINUX-057RAID rebuild targets the wrong device after a degraded mdadm recoveryThe array is degraded but recoverable, and the biggest risk now is re-adding or marking the wrong member while interpreting device names under pressure.LinuxAdvanced27 minProCICD-052Reusable workflow caller changes the OIDC subject and breaks deploy role trustThe same deployment worked as a repository-local workflow, but it fails after moving into a reusable workflow because the token subject no longer matches the original trust condition.CI/CDAdvanced27 minProCICD-032OIDC subject condition mismatch denies AWS deploy role assumptionGitHub Actions reaches AWS STS, but the trust policy rejects the web identity token because the subject or audience condition no longer matches the branch and environment path.CI/CDAdvanced28 minProSECURITY-003WAF rule deployment blocks admin API but misses the real attack pathA hotfix rule stops valid management traffic while the malicious request pattern still finds an unprotected endpoint.SecurityAdvanced28 minProCICD-026Promotion pipeline deploys stale image from previous commitThe promotion stage uses an artifact reference that looks correct but resolves to an older image digest after registry cleanup.CI/CDAdvanced29 minProCICD-040Terraform apply succeeds in staging but production backend locks a different state tableThe same pipeline logic passes against one workspace, but production never converges because the remote backend, state lock table, or workspace mapping differs subtly.CI/CDAdvanced30 minProNETWORK-139A CAPWAP access point reaches the controller, but DTLS setup failsLayer-3 reachability is fine, yet management onboarding stalls on the trust layer.NetworkIntermediate16 minProNETWORK-138A local preference change is present in policy, but without soft reconfiguration the edge never reevaluates existing paths until a clearThe route-map is correct, yet the live table still reflects yesterday's decision because policy reevaluation never happened.NetworkAdvanced16 minProNETWORK-155A routing summary is correct in normal conditions, but when the only specific route fails the summary still attracts traffic into a black holeAggregation reduced table size, yet it also masked the absence of any viable child route.NetworkIntermediate16 minProNETWORK-393A static summary route is valid while the tracking object for the real downstream next hop was repointed to an interface that stays up during failure during a staged decommissionThe summary remains installed long after the useful path is gone. The service still works through the primary path, but one dependency only fails when the old component is finally drained away.NetworkIntermediate16 minProNETWORK-345A BGP edge prefers the right path (Rollout Stuck)A BGP edge prefers the right path (Rollout Stuck) focuses on Routing And Failover Paths and asks the reader to isolate Rollout Stuck in Cisco. 실무에서는 rollout-stuck 이슈를 볼 때 DNS, 라우팅, ACL/방화벽, 목적지 응답을 계층별로 잘라서 확인하면 장애 구간을 훨씬 빠르게 좁힐 수 있습니다.NetworkAdvanced17 minProK8S-159A canary Service routes to the right pods, but topology spread on the new ReplicaSet sends all canary capacity to one zone and synthetic tests misjudge global readinessTraffic experiments are statistically misleading because one zone now dominates the canary population.KubernetesAdvanced17 minProCICD-138A deployment circuit breaker watches the startup probe, but the one-off migration pod shares the same label and trips the release incorrectlyApplication pods are healthy, yet rollout halts because the failure budget includes a different workload type with a separate lifecycle.CI/CDAdvanced17 minProCICD-151A deployment freeze opens for one hour, but the delayed approval queue starts the rollout after the window closes and the policy engine revokes credentials mid-releaseEverything was approved at the right time, yet execution drifted outside the governance boundary.CI/CDAdvanced17 minPro