Rollout Stuck
384 incident problems that show up as “Rollout Stuck”.
먼저 읽을 가이드
추천 문제
All problems (384)
CICD-252A queued ChatOps rerun inherits stale authorization after the original release freeze window already closed during a failover rehearsalThe command looks approved from the chat log while execution happens under a no-longer-valid auth context. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.CI/CDAdvanced17 minProNETWORK-330A route summary survives while every specific path behind it is now gone and traffic keeps choosing the black hole during a failover rehearsalAggregation stays healthy after the real forwarding options disappeared. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.NetworkIntermediate17 minProNETWORK-221A route-map matches the right prefix set while one additive community action is replaced instead of appended after a maintenance template changeThe route is still policy-matched, yet a downstream signal disappears because one action semantics was misunderstood. The path looked healthy before the template changed, but one inherited assumption no longer matches the live environment.NetworkAdvanced17 minProNETWORK-225A route-map matches the right prefix set while one additive community action is replaced instead of appended after a retention policy refreshThe route is still policy-matched, yet a downstream signal disappears because one action semantics was misunderstood. The operational object still exists somewhere in the system, but the lifecycle policy around its supporting state no longer matches reality.NetworkAdvanced17 minProNETWORK-223A route-map matches the right prefix set while one additive community action is replaced instead of appended after an environment identity renameThe route is still policy-matched, yet a downstream signal disappears because one action semantics was misunderstood. The functional path still exists, but one identity, namespace, or naming assumption still points at the previous environment contract.NetworkAdvanced17 minProNETWORK-119A route-policy regex matches the AS path set too broadly and blackholes partner prefixes that should stay externalTraffic loss starts after a policy cleanup because the new pattern captures more paths than the operator intended.NetworkAdvanced17 minProNETWORK-121A transit interface was left out of passive-interface default exceptions, and a rogue OSPF adjacency forms during an access switch replacementThe underlay works until maintenance introduces a neighbor on a segment that should never have participated in routing.NetworkAdvanced17 minProNETWORK-270A VRRP pair shares the gateway IP while one downstream ACL still permits only the previous virtual MAC during a failover rehearsalRedundancy is healthy and the dependent security policy remains bound to yesterday's identity. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.NetworkAdvanced17 minProNETWORK-144A VXLAN flood-and-learn segment still receives BUM traffic, but ARP suppression on one VTEP keeps a stale host mapping and east-west packets disappearThe overlay fabric is generally healthy, yet one stale optimization prevents correct endpoint learning.NetworkAdvanced17 minProCICD-132An ephemeral runner image misses the internal CA root and only private registry pulls fail after autoscaling adds new workersLegacy workers continue working, but new ones cannot trust the organization registry chain.CI/CDAdvanced17 minProCICD-375An infrastructure drift policy ignores deleted optional resources while a recovery run still expects their outputs to exist for rollback wiring during a staged decommissionThe live state looks acceptable until rollback tries to consume outputs from deleted optional blocks. The service still works through the primary path, but one dependency only fails when the old component is finally drained away.CI/CDAdvanced17 minProNETWORK-146An MPLS TE tunnel comes up, but autoroute announce is disabled on one node and normal traffic never uses the engineered pathThe tunnel exists, yet forwarding behavior does not change because one control flag was left off.NetworkAdvanced17 minProCICD-011Branch protection rules exist, but the deploy workflow pushes directly to mainCovers a deployment-policy problem where code-review protection exists but the automation account becomes a bypass path.CI/CDBeginner17 minProNETWORK-122eBGP TTL security is configured on one side only after the provider path gains an extra hop, and the session drops permanentlyBoth peers still have the right neighbors configured, yet the control-plane hardening assumption no longer matches reality.NetworkAdvanced17 minProCICD-084GitHub Environment protection waits foreverReviewers approve the release, but the gate never opens because the workflow reports status to a differently cased or aliased environment than the protected one.CI/CDAdvanced17 minProK8S-105Ingress canary header routing works for HTTP but gRPC requests ignore the split and all traffic stays on stableThe progressive delivery rule appears valid, but the gRPC path follows a different routing evaluation than the header-based HTTP test path.KubernetesAdvanced17 minProK8S-096PodSecurity admission blocks the debug container flow even though the base workload still runsThe app continues serving traffic, but emergency debugging fails because the current security profile denies the ephemeral container path.KubernetesAdvanced17 minProCICD-101Preview environment cleanup job deletes the release candidate namespace before smoke tests startA pull request environment vanishes moments before validation because the cleanup workflow no longer waits for the downstream smoke test status.CI/CDAdvanced17 minProLINUX-093Systemd path unit keeps relaunching a failed helperThe service appears to restart itself, but the real trigger is a path unit that keeps firing on the same file activity loop.LinuxAdvanced17 minProNETWORK-143A BGP blackhole community is set correctly, but the route reflector policy strips it before it reaches the transit edge and mitigation never activatesMitigation signaling exists at the source, yet it vanishes in the core policy path.NetworkAdvanced18 minPro