Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple Verifications running for a Stage #2142

Closed
jessesuen opened this issue Jun 11, 2024 · 4 comments
Closed

Multiple Verifications running for a Stage #2142

jessesuen opened this issue Jun 11, 2024 · 4 comments

Comments

@jessesuen
Copy link
Member

Description

Stages seem to be allowing multiple Verifications to be run at the same time. Each coincided with a promotion.

image
$ k get ar
NAME                                     STATUS    AGE
dev.01j02dz4tbp75sf7zmvgkw3d3j.9e5f6ab   Failed    16h
dev.01j02hycta7xsjz7xczamptk6c.9d167fb   Failed    14h
dev.01j03w1h1njwvj432nbh8m7xvk.a72c52c   Running   158m
dev.01j03wxxntp3a3xm5pbpdzzzkd.bd13218   Running   142m
dev.01j03z1dzstgnx5tw85ty3apxr.97465d1   Running   105m

I feel that we should only be allowing one at a time to happen.

We should also decide how Promotion should affect currently running Verifications. e.g. should it:

  • wait for current verification to complete, then immediately launch a new one against the freight?
  • terminate in-flight verification (since it's ambiguous what exactly was verified)?
  • block the promotion until verification is completed?

Steps to Reproduce

Promote something else while a verification is already running.

Version

v0.7.0
@krancour
Copy link
Member

Possibly a duplicate of #2128?

@hiddeco
Copy link
Contributor

hiddeco commented Jun 11, 2024

block the promotion until verification is completed?

I feel this would (again) steer more towards verification being an element of promotion, which based on the further discussion in #2128 does not appear to be true. In addition, it hypothetically opens a gap to e.g. quickly issue re-verifications to block a promotion from ever starting.

Given this, I am inclined to say we should wait for a running verification to complete (and maybe terminate it if there is new current Freight), before triggering a new verification.

@krancour
Copy link
Member

which based on the further discussion in #2128...

fwiw, my thoughts there were in no way definitive/final.

Let's hash this out f2f when time permits.

@krancour
Copy link
Member

Close enough to a duplicate of #2128 that I am closing this one to keep discussion all in one place.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants