Bug 1311471 - /var/log/skyring/skyring.log is missing timestamps
/var/log/skyring/skyring.log is missing timestamps
Status: CLOSED WONTFIX
Product: Red Hat Storage Console
Classification: Red Hat
Component: core (Show other bugs)
2
Unspecified Unspecified
unspecified Severity medium
: ---
: 3
Assigned To: Nishanth Thomas
sds-qe-bugs
: TestBlocker
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-02-24 05:28 EST by Martin Bukatovic
Modified: 2017-03-23 00:02 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-03-23 00:02:50 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Martin Bukatovic 2016-02-24 05:28:57 EST
Description of problem
======================

Skyring log file /var/log/skyring/skyring.log is missing timestamps in most
cases.

Version-Release number of selected component
============================================

rhscon-core-0.0.8-4.el7.x86_64
rhscon-ceph-0.0.6-4.el7.x86_64
rhscon-ui-0.0.14-1.el7.noarch

How reproducible
================

100 %

Steps to Reproduce
==================

1. Install skyring on server and prepare few hosts for cluster setup
2. Accept all nodes
3. Create cluster
4. See /var/log/skyring/skyring.log file on USM machine

Actual results
==============

Through skyring log file, timestamps are consistently missing.

See for example that in my case, there is much more lines without any timestamp
compared to lines with one:

~~~
$ grep -v  '^.*2016-02-..T' skyring.log | wc -l
21797
$ grep  '^.*2016-02-..T' skyring.log | wc -l
519
~~~

While this sometimes may make sense, eg:

~~~
local:
    ----------
    master.pem:
        aa:27:18:4d:66:c8:87:90:ac:59:2b:4d:2f:19:5c:72
    master.pub:
        f1:d1:4f:f8:59:b0:e6:ea:cb:bd:8c:d9:d2:97:bb:16
minions_pre:
    ----------
    mbukatov-usm2-node1.example.com:
        11:e4:b4:2a:d0:2c:0b:6c:dd:0a:f8:76:5e:a8:ac:e8
    mbukatov-usm2-node2.example.com:
        09:be:08:07:44:0f:2b:bb:fe:de:76:ee:cd:19:54:f4
    mbukatov-usm2-node3.example.com:
        ad:77:b0:93:41:aa:71:60:17:91:dd:00:25:f4:ec:a5
    mbukatov-usm2-node4.example.com:
        76:1c:3d:63:9c:39:e0:36:ca:6e:51:4d:e5:a6:ba:73
    mbukatov-usm2-node5.example.com:
        98:aa:33:42:df:3f:45:a1:38:c5:5e:31:8c:21:ed:ca
    mbukatov-usm2-node6.example.com:
        52:9a:82:54:23:ab:9f:65:cd:04:d3:22:96:a2:24:e1
~~~

Lines like this definitelly dererves a timestamp:

~~~
[negroni] Started POST /api/v1/unmanaged_nodes/mbukatov-usm2-node1.example.com/accept
[negroni] Started POST /api/v1/unmanaged_nodes/mbukatov-usm2-node6.example.com/accept
[negroni] Started POST /api/v1/unmanaged_nodes/mbukatov-usm2-node5.example.com/accept
[negroni] Started POST /api/v1/unmanaged_nodes/mbukatov-usm2-node4.example.com/accept
[negroni] Started POST /api/v1/unmanaged_nodes/mbukatov-usm2-node3.example.com/accept
[negroni] Started POST /api/v1/unmanaged_nodes/mbukatov-usm2-node2.example.com/accept
[negroni] Completed 202 Accepted in 28.596973ms
[negroni] Completed 202 Accepted in 48.605852ms
[negroni] Completed 202 Accepted in 48.976975ms
[negroni] Completed 202 Accepted in 52.039316ms
[negroni] Completed 202 Accepted in 60.727125ms
[negroni] Completed 202 Accepted in 71.907087ms
[negroni] Started GET /api/v1/tasks/0e34d5a0-42c8-448c-ae43-d01ff05e7feb
[negroni] Completed 200 OK in 3.453303ms
[negroni] Started GET /api/v1/tasks/a9c2266a-188d-4cb6-8dac-408712f84108
[negroni] Completed 200 OK in 2.751552ms
[negroni] Started GET /api/v1/tasks/49e00af5-ad78-4879-9fb9-5c6350913803
[negroni] Completed 200 OK in 4.150115ms
[negroni] Started GET /api/v1/tasks/2794283d-a6c3-4f26-b6f6-8a65f433cfaa
[negroni] Completed 200 OK in 5.874062ms
[negroni] Started GET /api/v1/tasks/4753d838-7472-41b5-9c98-c70956bdb8bb
[negroni] Completed 200 OK in 1.398299ms
[negroni] Started GET /api/v1/tasks/30a85de1-0442-4384-aefa-d3040f683c34
[negroni] Completed 200 OK in 3.68197ms
[negroni] Started GET /fonts/OpenSans-Bold-webfont.woff
~~~

Or this one, without a timestamp, I have no idea when it happened:

~~~
SIGABRT: abort
PC=0x7f9cfee685f7
signal arrived during cgo execution
~~~

Expected results
================

Most log entries in skyring log file /var/log/skyring/skyring.log have
a proper timestamp.

For example, all '[negroni]' entries and error handling.

Note You need to log in before you can comment on or make changes to this bug.