Bug 1805283

Summary: Make the 'short-precise' format the default output for kubelet node journal logs
Product: OpenShift Container Platform Reporter: Maciej Szulik <maszulik>
Component: NodeAssignee: Clayton Coleman <ccoleman>
Status: CLOSED ERRATA QA Contact: Weinan Liu <weinliu>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.4CC: aos-bugs, ccoleman, jokerman, schoudha, weinliu
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1804514 Environment:
Last Closed: 2020-07-13 17:16:23 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: 1804514    

Description Maciej Szulik 2020-02-20 15:54:43 UTC
The default format is short which is 'HH:MM:SS', but we want short-precise which is 'HH:MM:SS.DDDDDDDD'.  This will make output a lot easier to sort and compare to other results.

Backport to 4.3.

Comment 1 Maciej Szulik 2020-02-20 15:56:01 UTC
Merged in https://github.com/openshift/origin/pull/24564

Comment 4 Weinan Liu 2020-02-21 09:01:44 UTC
Verified to be fixed on 

$ oc version
Client Version: openshift-clients-4.3.0-201910250623-79-g5d15fd52
Server Version: 4.4.0-0.nightly-2020-02-17-211020
Kubernetes Version: v1.17.1

$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.4.0-0.nightly-2020-02-17-211020   True        False         23m     Cluster version is 4.4.0-0.nightly-2020-02-17-211020


$ oc debug node/ip-10-0-141-11.us-east-2.compute.internal
Starting pod/ip-10-0-141-11us-east-2computeinternal-debug ...
To use host binaries, run `chroot /host`
chroot /host
Pod IP: 10.0.141.11
If you don't see a command prompt, try pressing enter.
sh-4.2# chroot /host
sh-4.4#
sh-4.4# journalctl -u kubelet
-- Logs begin at Fri 2020-02-21 08:10:51 UTC, end at Fri 2020-02-21 08:57:09 UTC. --
Feb 21 08:15:52 ip-10-0-141-11 systemd[1]: Starting Kubernetes Kubelet...
Feb 21 08:15:53 ip-10-0-141-11 hyperkube[2070]: Flag --minimum-container-ttl-duration has been deprecated, Use --eviction-hard or --eviction-soft instead. Will be removed in a future versio>
Feb 21 08:15:53 ip-10-0-141-11 hyperkube[2070]: I0221 08:15:53.420008    2070 flags.go:33] FLAG: --add-dir-header="false"
Feb 21 08:15:53 ip-10-0-141-11 hyperkube[2070]: I0221 08:15:53.420151    2070 flags.go:33] FLAG: --address="0.0.0.0"
Feb 21 08:15:53 ip-10-0-141-11 hyperkube[2070]: I0221 08:15:53.420159    2070 flags.go:33] FLAG: --allowed-unsafe-sysctls="[]"
Feb 21 08:15:53 ip-10-0-141-11 hyperkube[2070]: I0221 08:15:53.420166    2070 flags.go:33] FLAG: --alsologtostderr="false"
Feb 21 08:15:53 ip-10-0-141-11 hyperkube[2070]: I0221 08:15:53.420172    2070 flags.go:33] FLAG: --anonymous-auth="true"
Feb 21 08:15:53 ip-10-0-141-11 hyperkube[2070]: I0221 08:15:53.420178    2070 flags.go:33] FLAG: --application-metrics-count-limit="100"
Feb 21 08:15:53 ip-10-0-141-11 hyperkube[2070]: I0221 08:15:53.420183    2070 flags.go:33] FLAG: --authentication-token-webhook="false"
Feb 21 08:15:53 ip-10-0-141-11 hyperkube[2070]: I0221 08:15:53.420188    2070 flags.go:33] FLAG: --authentication-token-webhook-cache-ttl="2m0s"
Feb 21 08:15:53 ip-10-0-141-11 hyperkube[2070]: I0221 08:15:53.420195    2070 flags.go:33] FLAG: --authorization-mode="AlwaysAllow"
Feb 21 08:15:53 ip-10-0-141-11 hyperkube[2070]: I0221 08:15:53.420201    2070 flags.go:33] FLAG: --authorization-webhook-cache-authorized-ttl="5m0s"
Feb 21 08:15:53 ip-10-0-141-11 hyperkube[2070]: I0221 08:15:53.420206    2070 flags.go:33] FLAG: --authorization-webhook-cache-unauthorized-ttl="30s"
Feb 21 08:15:53 ip-10-0-141-11 hyperkube[2070]: I0221 08:15:53.420211    2070 flags.go:33] FLAG: --azure-container-registry-config=""
Feb 21 08:15:53 ip-10-0-141-11 hyperkube[2070]: I0221 08:15:53.420215    2070 flags.go:33] FLAG: --boot-id-file="/proc/sys/kernel/random/boot_id"

<...snipping...>

@Maciej,
Btw, do we need to get the Target Release 4.5 updated?

Comment 5 Maciej Szulik 2020-02-21 12:15:39 UTC
> @Maciej,
> Btw, do we need to get the Target Release 4.5 updated?

See the dependant bug for a 4.4 version of this, this one is specifically for 4.5.

Comment 6 Weinan Liu 2020-02-25 13:35:11 UTC
@Maciej,

Got you. Would you mind me pushing the status back? I think it's early for an ON_QA status.

Comment 10 errata-xmlrpc 2020-07-13 17:16:23 UTC
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-2020:2409