-
Notifications
You must be signed in to change notification settings - Fork 252
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
[Bug]: Tablespace e2e test sometimes goes timeout #4606
Labels
bug 🐛
Something isn't working
Comments
sxd
added a commit
that referenced
this issue
May 20, 2024
The short timeout that is only used on tablespaces tests it was by default set to 5 seconds, this is a bit too short and it was producing some failures in some of the cloud environment tests. Closes #4606 Signed-off-by: Jonathan Gonzalez V <jonathan.gonzalez@enterprisedb.com>
sxd
added a commit
that referenced
this issue
May 20, 2024
The short timeout that is only used on tablespaces tests it was by default set to 5 seconds, this is a bit too short and it was producing some failures in some of the cloud environment tests. Closes #4606 Signed-off-by: Jonathan Gonzalez V <jonathan.gonzalez@enterprisedb.com>
sxd
added a commit
that referenced
this issue
May 21, 2024
The short timeout that is only used on tablespaces tests it was by default set to 5 seconds, this is a bit too short and it was producing some failures in some of the cloud environment tests. Closes #4606 Signed-off-by: Jonathan Gonzalez V <jonathan.gonzalez@enterprisedb.com>
NiccoloFei
pushed a commit
that referenced
this issue
May 24, 2024
The short timeout that is only used on tablespaces tests it was by default set to 5 seconds, this is a bit too short and it was producing some failures in some of the cloud environment tests. Closes #4606 Signed-off-by: Jonathan Gonzalez V <jonathan.gonzalez@enterprisedb.com>
NiccoloFei
pushed a commit
that referenced
this issue
May 27, 2024
The short timeout that is only used on tablespaces tests it was by default set to 5 seconds, this is a bit too short and it was producing some failures in some of the cloud environment tests. Closes #4606 Signed-off-by: Jonathan Gonzalez V <jonathan.gonzalez@enterprisedb.com>
sxd
added a commit
that referenced
this issue
May 28, 2024
The short timeout that is only used on tablespaces tests it was by default set to 5 seconds, this is a bit too short and it was producing some failures in some of the cloud environment tests. Closes #4606 Signed-off-by: Jonathan Gonzalez V <jonathan.gonzalez@enterprisedb.com>
sxd
added a commit
that referenced
this issue
May 29, 2024
The short timeout that is only used on tablespaces tests it was by default set to 5 seconds, this is a bit too short and it was producing some failures in some of the cloud environment tests. Closes #4606 Signed-off-by: Jonathan Gonzalez V <jonathan.gonzalez@enterprisedb.com>
mnencia
added a commit
that referenced
this issue
May 30, 2024
The short timeout, which is only used on tablespaces tests, is set to 5 seconds by default. This is too short and produced some failures in some cloud environment tests. Additionally, we stop logging errors that aren't errors at all while getting the pod logs. Closes #4606 Signed-off-by: Jonathan Gonzalez V <jonathan.gonzalez@enterprisedb.com> Signed-off-by: Niccolò Fei <niccolo.fei@enterprisedb.com> Signed-off-by: Jonathan Gonzalez V. <jonathan.abdiel@gmail.com> Co-authored-by: Niccolò Fei <niccolo.fei@enterprisedb.com> Co-authored-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com>
cnpg-bot
pushed a commit
that referenced
this issue
May 30, 2024
The short timeout, which is only used on tablespaces tests, is set to 5 seconds by default. This is too short and produced some failures in some cloud environment tests. Additionally, we stop logging errors that aren't errors at all while getting the pod logs. Closes #4606 Signed-off-by: Jonathan Gonzalez V <jonathan.gonzalez@enterprisedb.com> Signed-off-by: Niccolò Fei <niccolo.fei@enterprisedb.com> Signed-off-by: Jonathan Gonzalez V. <jonathan.abdiel@gmail.com> Co-authored-by: Niccolò Fei <niccolo.fei@enterprisedb.com> Co-authored-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> (cherry picked from commit 4b454e6)
mnencia
pushed a commit
that referenced
this issue
May 30, 2024
The short timeout, which is only used on tablespaces tests, is set to 5 seconds by default. This is too short and produced some failures in some cloud environment tests. Additionally, we stop logging errors that aren't errors at all while getting the pod logs. Closes #4606 Signed-off-by: Jonathan Gonzalez V <jonathan.gonzalez@enterprisedb.com> Signed-off-by: Niccolò Fei <niccolo.fei@enterprisedb.com> Signed-off-by: Jonathan Gonzalez V. <jonathan.abdiel@gmail.com> Co-authored-by: Niccolò Fei <niccolo.fei@enterprisedb.com> Co-authored-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> (cherry picked from commit 4b454e6)
mnencia
pushed a commit
that referenced
this issue
May 30, 2024
The short timeout, which is only used on tablespaces tests, is set to 5 seconds by default. This is too short and produced some failures in some cloud environment tests. Additionally, we stop logging errors that aren't errors at all while getting the pod logs. Closes #4606 Signed-off-by: Jonathan Gonzalez V <jonathan.gonzalez@enterprisedb.com> Signed-off-by: Niccolò Fei <niccolo.fei@enterprisedb.com> Signed-off-by: Jonathan Gonzalez V. <jonathan.abdiel@gmail.com> Co-authored-by: Niccolò Fei <niccolo.fei@enterprisedb.com> Co-authored-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> (cherry picked from commit 4b454e6)
dougkirkley
pushed a commit
to dougkirkley/cloudnative-pg
that referenced
this issue
Jun 11, 2024
The short timeout, which is only used on tablespaces tests, is set to 5 seconds by default. This is too short and produced some failures in some cloud environment tests. Additionally, we stop logging errors that aren't errors at all while getting the pod logs. Closes cloudnative-pg#4606 Signed-off-by: Jonathan Gonzalez V <jonathan.gonzalez@enterprisedb.com> Signed-off-by: Niccolò Fei <niccolo.fei@enterprisedb.com> Signed-off-by: Jonathan Gonzalez V. <jonathan.abdiel@gmail.com> Co-authored-by: Niccolò Fei <niccolo.fei@enterprisedb.com> Co-authored-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> Signed-off-by: Douglass Kirkley <dkirkley@eitccorp.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue already for this bug?
I have read the troubleshooting guide
I am running a supported version of CloudNativePG
Contact Details
No response
Version
1.23.1
What version of Kubernetes are you using?
1.30 (unsupported)
What is your Kubernetes environment?
Self-managed: kind (evaluation)
How did you install the operator?
YAML manifest
What happened?
Sometimes the tablespace tests (not all of them) will fail with a timeout like this:
Cluster resource
No response
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: