Bug 1744840
| Summary: | oc adm node-logs cannot get full logs due to 30 sec timeout | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Takayoshi Kimura <tkimura> |
| Component: | oc | Assignee: | Maciej Szulik <maszulik> |
| Status: | CLOSED WONTFIX | QA Contact: | zhou ying <yinzhou> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.2.0 | CC: | aos-bugs, hchiramm, jokerman, mfojtik, rkrawitz, somalley, tnozicka, yinzhou |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1728101 | Environment: | |
| Last Closed: | 2019-08-23 10:49:59 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1728101 | ||
The limit is to protect the API server from being DDoS-ed, I don't envision us extending that value. There are multiple workarounds as you've mentioned. If one of the provided does not work feel free to open an issue about that particular functionality. I'm closing the current bug as won't fix. The --since option workaround does work, also. See here: https://bugzilla.redhat.com/show_bug.cgi?id=1728101 *** Bug 1728101 has been marked as a duplicate of this bug. *** *** Bug 1740153 has been marked as a duplicate of this bug. *** |
Description of problem: oc adm node-logs cannot get full logs due to 30 sec timeout. > $ time oc adm node-logs ip-10-0-134-117.ap-northeast-1.compute.internal | gzip > log.gz > > real 0m30.821s > user 0m19.329s > sys 0m1.746s > > $ zcat log.gz | head > -- Logs begin at Fri 2019-07-05 10:15:42 UTC, end at Tue 2019-07-09 03:33:53 UTC. -- > Jul 05 10:15:42 ip-10-0-134-117 hyperkube[2264]: File "/usr/lib64/python2.7/SocketServer.py", line 334, in finish_request > > $ zcat log.gz | tail > Jul 06 19:04:11 ip-10-0-134-117 hyperkube[2264]: I0706 19:04:11.145001 2264 configmap.go:207] Received configMap openshift-dns/dns-default containing (1) pieces of data, 247 total bytes > Jul 06 19:04:11 ip-10-0-134-117 hyperkube[2264]: I0706 19:04:11.145583 2264 secret.go:206] Received secret openshift-dns/dns-token-p2cr6 containing (4) pieces of data, 11239 total bytes > > $ time oc adm node-logs ip-10-0-134-117.ap-northeast-1.compute.internal --tail=1000000 | gzip > log-tail.gz > > real 0m3.833s > user 0m2.217s > sys 0m0.216s > > $ $ zcat log-tail.gz | wc -l > 200002 > > $ zcat log-tail.gz | tail > Jul 09 03:37:32 ip-10-0-134-117 hyperkube[2073]: I0709 03:37:32.070347 2073 helpers.go:846] eviction manager: observations: signal=nodefs.inodesFree, available: 62299002, capacity: 62389184, time: 2019-07-09 03:37:32.062073369 +0000 UTC m=+87787.582782338 > Jul 09 03:37:32 ip-10-0-134-117 hyperkube[2073]: I0709 03:37:32.070368 2073 helpers.go:846] eviction manager: observations: signal=imagefs.available, available: 107220488Ki, capacity: 124768236Ki, time: 2019-07-09 03:37:32.062073369 +0000 UTC m=+87787.582782338 > > $ TZ=UTC date > Tue 09 Jul 2019 03:37:43 AM UTC Version-Release number of selected component (if applicable): OpenShift 4.1.4 AWS IPI How reproducible: Always Steps to Reproduce: 1. Perform oc adm node-logs with long-running node 2. 3. Actual results: oc adm node-logs command can get very first of the logs and finished, no error report Expected results: oc adm node-logs command can get full logs. Or at least it needs to report timeout error. Additional info: Workarounds are: - to use --tail option, but it can only get 200k lines max. The --since option doesn't work atm. - use ssh access