No timestamps or wrong format of timestamps in logfiles under fuel-master:/var/log
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Won't Fix
|
Medium
|
Valeriy Saharov | ||
6.0.x |
Won't Fix
|
Medium
|
Dmitry Ilyin | ||
7.0.x |
Won't Fix
|
Medium
|
Fuel Library (Deprecated) | ||
8.0.x |
Won't Fix
|
Medium
|
Fuel Library (Deprecated) | ||
Mitaka |
Won't Fix
|
Medium
|
Valeriy Saharov |
Bug Description
Logfiles should contain a timestamp with the correct format .
The correct format is as shown below
2015-01-
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.
Changed in fuel: | |
importance: | Undecided → Medium |
assignee: | nobody → Fuel Library Team (fuel-library) |
milestone: | none → 6.1 |
Changed in fuel: | |
status: | New → Confirmed |
Changed in fuel: | |
assignee: | Fuel Library Team (fuel-library) → Dmitry Ilyin (idv1985) |
Changed in fuel: | |
status: | Confirmed → Won't Fix |
no longer affects: | fuel/6.1.x |
tags: | added: qa-afree-7.0 |
tags: |
added: need-bp removed: feature |
tags: |
added: qa-agree-7.0 removed: qa-afree-7.0 |
Changed in fuel: | |
assignee: | Dmitry Ilyin (idv1985) → Fuel Library Team (fuel-library) |
milestone: | 6.1 → 8.0 |
status: | Won't Fix → Confirmed |
no longer affects: | fuel/8.0.x |
tags: | added: area-library |
tags: | added: wontfix-risky |
Changed in fuel: | |
status: | In Progress → Won't Fix |
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