Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1728910

Summary: oc adm node-logs does not honor --since
Product: OpenShift Container Platform Reporter: Brian 'redbeard' Harrington <bharring>
Component: ocAssignee: Maciej Szulik <maszulik>
Status: CLOSED DUPLICATE QA Contact: zhou ying <yinzhou>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.1.zCC: aos-bugs, jokerman, mfojtik, tnozicka
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: Environment:
Last Closed: 2019-07-11 08:58:57 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 Brian 'redbeard' Harrington 2019-07-11 00:54:44 UTC
Description of problem:
When attempting to use oc adm node-logs to collect journal messages the oc command does not honor the syntax described by journalctl:

[~/openshift-install-02cd6e91]$ oc adm node-logs ip-192-168-179-98.us-west-1.compute.internal --since="2019-07-10 00:00:00"
error: ip-192-168-179-98.us-west-1.compute.internal the server rejected our request for an unknown reason
[~/openshift-install-02cd6e91]$ oc adm node-logs ip-192-168-179-98.us-west-1.compute.internal --since="2019-07-10"
error: ip-192-168-179-98.us-west-1.compute.internal the server rejected our request for an unknown reason
[~/openshift-install-02cd6e91]$ oc adm node-logs ip-192-168-179-98.us-west-1.compute.internal --since="2019-07-04"
error: ip-192-168-179-98.us-west-1.compute.internal the server rejected our request for an unknown reason

It is possible to collect logs from the host:

[~/openshift-install-02cd6e91]$ oc adm node-logs ip-192-168-179-98.us-west-1.compute.internal --tail=3
-- Logs begin at Mon 2019-07-01 19:05:56 UTC, end at Thu 2019-07-11 00:49:55 UTC. --
Jul 10 18:20:41 ip-192-168-179-98 systemd-shutdown[1]: Syncing filesystems and block devices.
Jul 10 18:20:41 ip-192-168-179-98 systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Jul 10 18:20:41 ip-192-168-179-98 systemd-journald[95173]: Journal stopped
-- Logs begin at Mon 2019-07-01 19:05:56 UTC, end at Thu 2019-07-11 00:49:55 UTC. --
Jul 11 00:49:52 ip-192-168-179-98 hyperkube[845]: I0711 00:49:52.505309     845 eviction_manager.go:321] eviction manager: no resources are starved
Jul 11 00:49:53 ip-192-168-179-98 hyperkube[845]: I0711 00:49:53.400791     845 prober.go:118] Readiness probe for "sdn-gslft_openshift-sdn(db32b877-a340-11e9-bc85-022e44d1f502):sdn" succeeded
Jul 11 00:49:55 ip-192-168-179-98 hyperkube[845]: I0711 00:49:55.488391     845 prober.go:118] Liveness probe for "sdn-gslft_openshift-sdn(db32b877-a340-11e9-bc85-022e44d1f502):sdn" succeeded



[~/openshift-install-02cd6e91]$ oc version
Client Version: version.Info{Major:"4", Minor:"1+", GitVersion:"v4.1.4-201906271212+6b97d85-dirty", GitCommit:"6b97d85", GitTreeState:"dirty", BuildDate:"2019-06-27T18:11:21Z", GoVersion:"go1.11.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.4+c62ce01", GitCommit:"c62ce01", GitTreeState:"clean", BuildDate:"2019-06-27T18:14:14Z", GoVersion:"go1.11.6", Compiler:"gc", Platform:"linux/amd64"}




Version-Release number of selected component (if applicable):
Client Version: version.Info{Major:"4", Minor:"1+", GitVersion:"v4.1.4-201906271212+6b97d85-dirty", GitCommit:"6b97d85", GitTreeState:"dirty", BuildDate:"2019-06-27T18:11:21Z", GoVersion:"go1.11.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.4+c62ce01", GitCommit:"c62ce01", GitTreeState:"clean", BuildDate:"2019-06-27T18:14:14Z", GoVersion:"go1.11.6", Compiler:"gc", Platform:"linux/amd64"}


Likely related to #1728105

Comment 1 Brian 'redbeard' Harrington 2019-07-11 00:56:16 UTC
*** Bug 1728911 has been marked as a duplicate of this bug. ***

Comment 2 Brian 'redbeard' Harrington 2019-07-11 00:56:37 UTC
*** Bug 1728912 has been marked as a duplicate of this bug. ***

Comment 3 Tomáš Nožička 2019-07-11 08:58:57 UTC
The only difference seems to be "today" vs. "2019-07-10 00:00:00", I am gonna put that comment into https://bugzilla.redhat.com/show_bug.cgi?id=1728105 as I think this is the same bug and we can track it there as well

*** This bug has been marked as a duplicate of bug 1728105 ***