No timestamps or wrong format of timestamps in logfiles under fuel-master:/var/log

[Aleksey Zvyagintsev]

Logfiles should contain a timestamp with the correct format .

The correct format is as shown below
2015-01-14T12:18:23.887490+00:00 (rfc3339)

The format provided above is the expected format. Other formats, containing the same information are also accepted, but all logs shall have the same timestamp format and all logs shall have timestamps.

##
Briefly - fuel-master itself(and docker containers) create a lot of unstructured and timestamped files and logs during install process.
I can suggest the next flow, which partially can help:
1)Add in puppet(host-only) fuel-master-rsyslog configuration step(before docker builds)

2) fix pre-system tools logging (fuel-menu \ anaconda logs( its real ?) )

3) configure correct redirecting from docker containers.

[Vladimir Kuklin (vkuklin)]

Fixing this bug takes too much time for 6.1 as we are reaching code freeze stage. This bug won't be fixed in 6.1 milestone

[Nastya Urlapova (aurlapova)]

Folks, please set one correct status for 6.1.

[Vladimir Kuklin (vkuklin)]

should be moved to 8.0 - should be converted into blueprint and split into a set of tasks for each particular service. requires a lot of work and is not feasible in 7.0

[Matthew Mosesohn (raytrac3r)]

Since this is a large task, it should be a feature

[Valeriy Saharov (vsakharov)]

It is possible to change default timestamp in the system logs (messages, auth.log, cron.log, daemon.log, debug, kern.log, syslog) and in the *-all.log (nova-all.log, glance-all.log, neutron-all.log and others) by adding "$ActionFileDefaultTemplate RSYSLOG_FileFormat" line in the each config file of rsyslog.d/. But I don't think that it is a good and full decision.

[Valeriy Saharov (vsakharov)]

It is should be the blueprint feature in the 10.0.