fix: assert keptn-cert-manager integration test more precisely #3258
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.
Description
Since the
testcertificate
integration test does restartlifecycle-operator
andmetrics-operator
Deployments, it should properly assert that the pods are running after the restart. If this is not the case after the restart -> chainsaw continues with another test (non-blocking-deployment
), but since the pods are not yet up and running, it fails.Also there was a need to increase the
execTimeout
in the chainsaw configuration to allow the scripts with retry logic to be executed for longer than the default 5s