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

v0.11 + bundles fail with API relation changed hook #41

Open
lazypower opened this issue Apr 8, 2015 · 2 comments
Open

v0.11 + bundles fail with API relation changed hook #41

lazypower opened this issue Apr 8, 2015 · 2 comments

Comments

@lazypower
Copy link
Collaborator

These are easily fixed up with a juju resolved -r, however the response coming from kubernetes-master is that the minion is already registered.

@mbruzek
Copy link
Collaborator

mbruzek commented Apr 8, 2015

@chuckbutler
This could be related to a different response code. We need to look at the log messages on why the relation failed. I pushed a fix for the different HTTP response code, to the kubernetes charms that is not vendored or maybe you didn't pull the latest kubernetes charm code from github. What I found was the kubernetes hook would "fail" after the registration code, but were successfully registered after all.

I also noticed that the Kubernetes API itself has changed in more modern versions (greater than v0.8.1) of the api-server. Created an issue against the kubernetes charm about this. They may be making making non backward compatible changes to the registration API in this pre v1.0 release that we need to know about and fix in the charm code.

@lazypower
Copy link
Collaborator Author

Right, and this is related to my findings @mbruzek - the bug here is to track that with my mass bundle reorgnization that i've been working on + testing.

I've got an aggregate of the logs to dive through and query, but a grep shows it is indeed related to the status code bug. I need to rebase the subordinate conversion code w/ your latest changes and validate again.

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

No branches or pull requests

2 participants