Bug 1728105
| Summary: | oc adm node-logs --since today option doesn't work | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Takayoshi Kimura <tkimura> |
| Component: | oc | Assignee: | Sally <somalley> |
| Status: | CLOSED ERRATA | QA Contact: | zhou ying <yinzhou> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.1.0 | CC: | aos-bugs, bharring, jokerman, mfojtik, somalley, tnozicka |
| Target Milestone: | --- | ||
| Target Release: | 4.1.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-08-28 19:54:45 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Takayoshi Kimura
2019-07-09 03:52:55 UTC
this seems to be the case with other --since arguments as well like "2019-07-10 00:00:00" in https://bugzilla.redhat.com/show_bug.cgi?id=1728910 *** Bug 1728910 has been marked as a duplicate of this bug. *** I ran with: oc adm node-logs ip-10-0-137-206.us-west-2.compute.internal --since today --loglevel=9, saw this: I0808 12:49:50.754508 21890 request.go:942] Response Body: parameter 'since' is invalid: date must be a relative time of the form '(+|-)[0-9]+(s|m|h|d)' or a date in 'YYYY-MM-DDTHH:MM:SSZ' form error: ip-10-0-137-206.us-west-2.compute.internal the server rejected our request for an unknown reason Then ran with this: oc adm node-logs ip-10-0-137-206.us-west-2.compute.internal --since -1d That worked :) Work for you? Confirmed with Client Version: v4.1.11: `oc adm node-logs ip-10-0-128-221.ap-northeast-2.compute.internal --since -1d --loglevel=9` works fine. ` oc adm node-logs ip-10-0-128-221.ap-northeast-2.compute.internal --since today --loglevel=9` I0809 17:48:16.984803 21034 loader.go:359] Config loaded from file /root/kubeconfig I0809 17:48:16.991795 21034 loader.go:359] Config loaded from file /root/kubeconfig .... I0809 17:48:17.729511 21034 request.go:942] Response Body: parameter 'since' is invalid: date must be a relative time of the form '(+|-)[0-9]+(s|m|h|d)' or a date in 'YYYY-MM-DDTHH:MM:SSZ' form error: ip-10-0-128-221.ap-northeast-2.compute.internal the server rejected our request for an unknown reason F0809 17:48:17.729567 21034 helpers.go:116] I think the error info is not accurate. I think the error msg is sufficient. When passing '--since today' you'll see: 'I0809 17:48:17.729511 21034 request.go:942] Response Body: parameter 'since' is invalid: date must be a relative time of the form '(+|-)[0-9]+(s|m|h|d)' To guide you to use '--since -1d' instead. The Go net/http.StatusBadRequest' error is converted by k8s apimachinery into "the server rejected our request for an unknown reason" Ok, per https://bugzilla.redhat.com/show_bug.cgi?id=1728105#c4, will verify this issue. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2547 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |