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

hazelcast example is broken #7731

Closed
caesarxuchao opened this issue May 4, 2015 · 8 comments · Fixed by #8023
Closed

hazelcast example is broken #7731

caesarxuchao opened this issue May 4, 2015 · 8 comments · Fixed by #8023
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.

Comments

@caesarxuchao
Copy link
Member

I followed the instructions in the tutorial and got this output:

$kubectl get pods hazelcast
POD         IP           CONTAINER(S)   IMAGE(S)              HOST                                     LABELS           STATUS    CREATED         MESSAGE
hazelcast   10.244.0.5                                        kubernetes-minion-7jsw/130.211.122.180   name=hazelcast   Running   About an hour   
                         hazelcast      pires/hazelcast-k8s                                                             Running   9 seconds       last termination: exit code 1

Note the "last termination: exit code 1".

And here is the log.

It seems to be a problem of hazelcast rather than Kubernetes. @pires @nikhiljindal

@nikhiljindal nikhiljindal added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. labels May 4, 2015
@nikhiljindal
Copy link
Contributor

@pires: Cant assign the issue to you, but I assume you are the right person to look at this?

@pires
Copy link
Contributor

pires commented May 4, 2015

@nikhiljindal I will take a look, yes but this has been changed recently, even by the user who just opened this ticket. How did his PR got merged without testing, I wonder?

@caesarxuchao what version of Kubernetes is this?

@caesarxuchao
Copy link
Member Author

It's 0.16.0.

In that PR, I updated the .yaml files to use the latest API version (v1beta3). I tested the original .yaml files, which are using v1beta1 API, and it causes the same problem.

@nikhiljindal, maybe revert that merge until @pires has a look?

@pires
Copy link
Contributor

pires commented May 4, 2015

@caesarxuchao my only question is why merge something that wasn't working in the first place? No harm done. I will try with your changes and without, but most probably it's something related to how the apiserver replies now and the library I'm using.

@caesarxuchao
Copy link
Member Author

@pires I will take caution next time. Thanks.

@pires
Copy link
Contributor

pires commented May 9, 2015

PR is up, please review.

@caesarxuchao
Copy link
Member Author

aha, endpoints contain a list of subsets...that's why my fix to cassandra is not working yet

@pires
Copy link
Contributor

pires commented May 10, 2015

@caesarxuchao yeah, tried to discuss that with you over IRC, but you don't seem to have received my messages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants