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

set high default api initialDelaySeconds #1957

Merged
merged 1 commit into from
Sep 6, 2024
Merged

Conversation

s2-ctraut
Copy link
Collaborator

Checklist

  • I have followed (at least) the PR section of the contributing guide.
  • [X ] I fixed all necessary PR warnings
  • [ X] The commit history is clean
  • The E2E tests are passing
  • [ X] If possible, the issue has been divided into more subtasks
  • [X ] I did a self review before requesting a review from another team member

Description

Creating sandboxes fails because the api pod is killed before it reaches liveness. Setting a very high value for initialDelaySeconds prevents being killed in this phase. The initial phase takes very long because filling the database with sample data takes quite a time.

How to test

Timeouts are environment specific. A final test can only be done on the final (prod) systems.

@openkfwCI
Copy link

openkfwCI commented Aug 29, 2024

NotesTime
Note for Reviewer: E2E tests on pipeline 60250 on remote server failedThu, 29 Aug 2024 09:40:08 +0000

Generated by E2E-Test

@galethil galethil merged commit 1846c59 into main Sep 6, 2024
30 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants