-
Notifications
You must be signed in to change notification settings - Fork 67
Closed
Description
Describe the bug
CI is failing on main
Version of Helm and Kubernetes:
What happened:
It's buried in the logs, but this seems to be the closest message I could find (this was in the events)
Error: UPGRADE FAILED: timed out waiting for the condition
...
4m26s Warning Unhealthy pod/couchdb-bn6xfmonab-couchdb-2 spec.containers{couchdb} kubelet, chart-testing-control-plane Readiness probe failed: Get "http://10.244.0.11:5984/_up": dial tcp 10.244.0.11:5984: connect: connection refused 4m26s 1 couchdb-bn6xfmonab-couchdb-2.16fa469e8b01115a
...
5m3s Warning FailedToUpdateEndpoint endpoints/couchdb-bn6xfmonab-svc-couchdb endpoint-controller Failed to update endpoint couchdb-bn6xfmonab/couchdb-bn6xfmonab-svc-couchdb: Operation cannot be fulfilled on endpoints "couchdb-bn6xfmonab-svc-couchdb": the object has been modified; please apply your changes to the latest version and try again 5m3s 1 couchdb-bn6xfmonab-svc-couchdb.16fa4695ef4ad529
I am suspicious that the issue with "upgrade" failing is related to #78
What you expected to happen: Pass CI
How to reproduce it (as minimally and precisely as possible): Look at CI on main π
Anything else we need to know:
discostur
Metadata
Metadata
Assignees
Labels
No labels