CI/CD Release Safety
105 incident problems about CI/CD Release Safety. Start with the reviewed ones.
먼저 읽을 가이드
추천 문제
All problems (105)
CICD-072GitHub Actions matrix deploy runs twice in productionThe workflow looks serialized, but two production deploys still overlap because the concurrency group ignores environment or region and only keys on the branch name.CI/CDAdvanced19 minProCICD-104Image promotion copies the manifest list but forgets the arm64 digest and only one node pool fails after releaseThe promoted tag looks valid in the registry, yet arm64 workers cannot pull because the multi-arch index lost a platform-specific child image during promotion.CI/CDAdvanced19 minProCICD-536A reusable workflow signs container images correctlyA reusable workflow signs container images correctly focuses on ci-cd-release-safety and asks the reader to isolate Permission Denied in GitHub. 실무에서는 ci-cd-release-safety 문제를 볼 때 실패 단계만 보지 말고 최근 변경, 이미지 태그, 시크릿 주입, 롤백 가능 여부를 먼저 함께 확인하는 편이 빠릅니다.CI/CDIntermediate20 minProCICD-096Rollback policy depends on ALB 5xx but the failure is only visible in gRPC status codesThe release is unhealthy, yet rollback never triggers because the monitored signal ignores application-layer failure semantics used by this service.CI/CDAdvanced20 minProCICD-067Argo Rollouts analysis never promotesTraffic and pods look healthy, yet automated promotion never happens because the analysis provider keeps evaluating metrics for an old release label set.CI/CDAdvanced22 minProCICD-061Argo CD app-of-apps sync waves leave the platform upgrade stuck on a child dependencyThe root application looks healthy, but one child app never becomes ready because the sync ordering assumes a dependency finished before its CRDs actually became usable.CI/CDAdvanced24 minProCICD-120Release note automation rewrites the semantic version tag into a prerelease suffix and downstream promotion logic refuses the artifactThe published artifact exists, but the promotion controller rejects it because the computed version string no longer matches the expected stable pattern.CI/CDAdvanced15 minProCICD-134A dependency proxy serves a cached package manifest after the source package was revoked, and downstream builds keep resolving the unsafe versionUpstream fixed the issue, but the local acceleration layer preserved the vulnerable metadata view.CI/CDIntermediate16 minProCICD-144A merge queue rebases the branch after tests pass, but the artifact fingerprint still reflects the pre-rebase commit and provenance checks reject the releaseThe code intent did not change much, yet artifact identity no longer matches the merge result the repository now points at.CI/CDIntermediate16 minProCICD-210A release exception is approved while its audit evidence never reaches the archive during a failover rehearsalOperations can continue in the moment, yet the governance record for why it happened is incomplete. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.CI/CDIntermediate16 minProCICD-129A feature-flag migration job starts before the secret rollout reaches the canary pods, and the flag backend rejects the writesThe release order seems safe, yet one dependency chain still lags behind the job that assumes it is ready.CI/CDAdvanced17 minProCICD-363A migration approval checks the application schema version while one asynchronous worker still runs the old reader contract in parallel during a staged decommissionThe release gate inspects the main service and misses the parallel consumer that still depends on the old shape. The service still works through the primary path, but one dependency only fails when the old component is finally drained away.CI/CDAdvanced17 minProCICD-294A package provenance check validates one tarball while the deploy step consumes a repacked archive from a mirror during a failover rehearsalSupply-chain checks pass on the source artifact, but the runtime path uses a derived archive that was never verified. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.CI/CDIntermediate17 minProCICD-141A release candidate is promoted from staging with the right image digest, but the production values file still points at the old feature-flag namespaceThe artifact is correct, yet behavior differs because runtime configuration still references an earlier control-plane context.CI/CDAdvanced17 minProCICD-192An artifact retention job keeps the image and removes the detached attestation during a failover rehearsalThe primary artifact remains available while admission or provenance checks lose the supporting proof they depend on. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.CI/CDIntermediate17 minProCICD-276Preview environment teardown removes DNS before certificate validation jobs finish probing the old hostname during a failover rehearsalThe environment lifecycle cleanup is correct for cost control and too early for the remaining verification path. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.CI/CDIntermediate17 minProCICD-121Protected environment reviewers are configured, but a branch rename leaves the production rule attached to the old pattern and deployment bypasses approvalThe release pipeline still sees a valid environment, yet the protection logic no longer matches the new main branch name the team now uses.CI/CDAdvanced17 minProCICD-387A canary job compares median latency while one percentile tail explodes only for a tenant class routed through a different auth provider during a staged decommissionAggregate health stays green while a routed subset proves the release is unsafe. The service still works through the primary path, but one dependency only fails when the old component is finally drained away.CI/CDAdvanced18 minProCICD-150A canary metric query excludes the holiday traffic segment and the release looks successful onlyThe analysis engine reports low error rates, yet its sampling window omits the exact traffic cohort that reveals the bug.CI/CDAdvanced18 minProCICD-282A deployment gate reuses the latest successful build from the wrong branch lineage during a failover rehearsalThe artifact is valid, but the gate promotes a build that never belonged to the current release branch. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.CI/CDAdvanced18 minPro