workflows/L4LB: Reprovision if vagrant up fails #17339
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Make sure that a subsequent call to "vagrant up" does the provisioning if a previous call has failed. Otherwise, we will risk running the L4LB suite on the VM with missing dependencies. Suggested-by: Paul Chaignon <paul@cilium.io> Signed-off-by: Martynas Pumputis <m@lambda.lt>
brb
added
area/CI
pchaigno
approved these changes
Sep 8, 2021
nbusseneau
approved these changes
Sep 8, 2021
pchaigno
added
the
ready-to-merge
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Make sure that a subsequent call to "vagrant up" does the provisioning
if a previous call has failed. Otherwise, we will risk running the L4LB
suite on the VM with missing dependencies.
Suggested-by: Paul Chaignon paul@cilium.io
Signed-off-by: Martynas Pumputis m@lambda.lt
Fix #17336