-
Notifications
You must be signed in to change notification settings - Fork 172
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
Add postgres pod status check for k8s tests in CI #1320
Conversation
Deploying astronomer-cosmos with Cloudflare Pages
|
1f58d28
to
32cff3a
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1320 +/- ##
=======================================
Coverage 95.85% 95.85%
=======================================
Files 67 67
Lines 3983 3983
=======================================
Hits 3818 3818
Misses 165 165 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great, thanks a lot, @pankajkoti ! Crossed fingers this will solve the issue.
It appears we have a flaky Kubernetes test that failed in PR #1313. As shown in the error log here, the PostgreSQL pod did not reach the ready state and instead entered an error status. Since the cause of the error status is unclear, this PR introduces a status check for the PostgreSQL pod to ensure it becomes fully running and healthy. If the pod enters an ERROR state, we now run a
kubectl describe
command on the pod to capture the event logs for debugging. The test will also exit with an error code of 1 to prevent further execution.related: #1319