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.

Sign up for GitHub

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

Jump to bottom

Fix broken CI on main #88

Closed
colearendt opened this issue Jun 20, 2022 · 1 comment · Fixed by #89
Closed

Fix broken CI on main #88

colearendt opened this issue Jun 20, 2022 · 1 comment · Fixed by #89

Comments

@colearendt
Copy link
Contributor

colearendt commented Jun 20, 2022 •
edited

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:https://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:
colearendt added a commit to colearendt/couchdb-helm that referenced this issue Jun 20, 2022
@colearendt
auto-generate the erlangCookie variable
27ad421 
related to apache#78, apache#88. We auto-generate the secret if it is not provided, and then continue to use that value on upgrades rather than auto-generating fresh each time.
colearendt added a commit to colearendt/couchdb-helm that referenced this issue Jun 20, 2022
@colearendt
auto-generate the erlangCookie variable
e5f4fb7 
related to apache#78, apache#88. We auto-generate the secret if it is not provided, and then continue to use that value on upgrades rather than auto-generating fresh each time.
@discostur discostur mentioned this issue Jun 22, 2022
Closed
@colearendt colearendt mentioned this issue Aug 4, 2022
Merged
4 tasks
colearendt added a commit to colearendt/couchdb-helm that referenced this issue Sep 19, 2022
@colearendt
auto-generate the erlangCookie variable
9c2f763 
related to apache#78, apache#88. We auto-generate the secret if it is not provided, and then continue to use that value on upgrades rather than auto-generating fresh each time.
@colearendt
Copy link
Contributor Author

This is fixed by #89

willholley pushed a commit that referenced this issue Oct 24, 2022
@colearendt @willholley
auto-generate the erlangCookie variable
3024366 
related to #78, #88. We auto-generate the secret if it is not provided, and then continue to use that value on upgrades rather than auto-generating fresh each time.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Auto-generate a stateful erlangCookie colearendt/couchdb-helm
1 participant
@colearendt