fix(gitops): correct stale users digest, pruned from registry before gitops was updated
All checks were successful
sync-to-forgejo / sync (push) Successful in 8s
All checks were successful
sync-to-forgejo / sync (push) Successful in 8s
backend-release-state.tsv referenced sha256:0548c99be..., which the registry's keep-2 prune step already garbage-collected. The live pod is actually running sha256:c5ec4ab3..., a valid, newer digest that was never recorded here - likely a write-order race between concurrent matrix jobs retrying pushes to this branch. Correct the record to match reality so the deployment can be safely restarted/rescheduled.
This commit is contained in:
parent
23c6f70ae4
commit
ce81802ad2
2 changed files with 2 additions and 2 deletions
|
|
@ -1,6 +1,6 @@
|
|||
gateway sha256:2ba654f8c224a4bead4a30bb170160220ac1f4d04364bbcea8e37abc3828606c 2
|
||||
companies sha256:8832bfbdfd1162d57732eb227a851081304ebeeaca52d94214b5ca360709315a 1
|
||||
users sha256:0548c99be54d09dbbc39fa8bbb74fe3d9efe58a36db70d9d263d24e4ba8999fc 1
|
||||
users sha256:c5ec4ab3f48daba8e77813ea088671e8388e2c54f0ed81dd7d9f955d31f56f14 1
|
||||
jobs sha256:57e587a56dece125ef7f0a3313470e58f4e25cb0d1708a6ff5bd0ba6dc012063 1
|
||||
leads sha256:9b5f33dbcb79f03feeea3d90f7d7894f96a7be9dfa3c611915f7786fa4f2dbcb 1
|
||||
job-seekers sha256:dbfff366a8d175874b33d6889fa3a1f9f88e622db0a33d0ab82fbba94e74b3f1 1
|
||||
|
|
|
|||
|
|
|
@ -32,7 +32,7 @@ spec:
|
|||
spec:
|
||||
containers:
|
||||
- name: users
|
||||
image: ci.nxtgauge.com/ashwin/nxtgauge-rust-users@sha256:0548c99be54d09dbbc39fa8bbb74fe3d9efe58a36db70d9d263d24e4ba8999fc
|
||||
image: ci.nxtgauge.com/ashwin/nxtgauge-rust-users@sha256:c5ec4ab3f48daba8e77813ea088671e8388e2c54f0ed81dd7d9f955d31f56f14
|
||||
---
|
||||
apiVersion: apps/v1
|
||||
kind: Deployment
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue