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

"Cluster level logging using Elasticsearch" breaks when master stops exporting pre-v1beta3 APIs #7420

Closed
nikhiljindal opened this issue Apr 28, 2015 · 1 comment
Closed

"Cluster level logging using Elasticsearch" breaks when master stops exporting pre-v1beta3 APIs #7420

nikhiljindal opened this issue Apr 28, 2015 · 1 comment
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
v1.0

Comments

@nikhiljindal
Copy link
Contributor

While testing for #5475, I found that "Cluster level logging using Elasticsearch" breaks when master stops exporting pre-v1beta3 APIs.
Here are the logs:

STEP: Checking all the log lines were ingested into Elasticsearch
After 9m52.664076986s expecting to find 200 log lines but saw only 0

• Failure [709.321 seconds]
Cluster level logging using Elasticsearch
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/es_cluster_logging.go:47
  should check that logs from pods on all nodes are ingested into Elasticsearch [It]
  /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/es_cluster_logging.go:46

  Failed to find all 200 log lines

  /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/es_cluster_logging.go:337

On some debugging, I found that we are sending a request to

api/v1beta3/proxy/namespaces/default/services/elasticsearch-logging/_search?q=log:es_logging_4352synthlogger&size=400

which is returning

"hits":{"total":0,"max_score":0.0,"hits":[]}

Not sure why it breaks.

@satnam6502 Any idea?
@a-robinson a-robinson added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. team/cluster labels Apr 28, 2015
@a-robinson a-robinson added this to the v1.0 milestone Apr 28, 2015
@nikhiljindal
Copy link
Contributor Author

Dup of #7453

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
v1.0
Development

No branches or pull requests
2 participants
@a-robinson @nikhiljindal