-
Notifications
You must be signed in to change notification settings - Fork 2.7k
kops jobs do not dump kube-scheduler, kube-ontroller-manager, kube-proxy, etc. logs #2397
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
Comments
justinsb
added a commit
to justinsb/kubernetes
that referenced
this issue
Apr 4, 2017
We make the files world-readable, so that installation techniques that lock down the logfiles can still be dumped. Issue kubernetes/test-infra#2397
Trying out a |
k8s-github-robot
pushed a commit
to kubernetes/kubernetes
that referenced
this issue
Apr 4, 2017
Automatic merge from submit-queue cluster/log-dump - chmod files before dumping We make the files world-readable, so that installation techniques that lock down the logfiles can still be dumped. Issue kubernetes/test-infra#2397 ```release-note NONE ```
/assign @justinsb |
change to cluster/log-dump fixed it, no more permission denied errors in recent jobs :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For instance, in this random recent PR job https://storage.googleapis.com/kubernetes-jenkins/pr-logs/pull/41929/pull-kubernetes-e2e-kops-aws/19348/build-log.txt we run cluster/log-dump.sh and get
Here's what /var/log looks like in a kops cluster:
LOG_DUMP_SSH_USER is
admin
, who doesn't have permissions to read & copy the file.This could be a kops issue, I don't know what the standard is for setting permissions on these log files.
The text was updated successfully, but these errors were encountered: