Heat logs too big
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
High
|
Steve Baker | ||
tripleo |
Fix Released
|
High
|
Unassigned |
Bug Description
On the tripleo HA jobs at the moment the undercloud tarball artifact is coming in around 26MB
From the looks of it the majority of this is comming from heat-engine.log and the journal log (which contains the same heat-engine log entries in it in a binary non zip friendly format)
We have 100's of 1000's of log entries of the format
Sep 24 07:24:21 instack.localdomain heat-engine[10240]: 2015-09-24 06:24:21.089 10240 INFO heat.engine.
JOBLOGS ]$ ls -lh heat/heat-
-rw-r--r--. 1 derekh derekh 65M Sep 24 07:53 heat/heat-
-rw-r-----. 1 derekh derekh 128M Sep 24 07:24 journal/
-rw-r-----. 1 derekh derekh 128M Sep 24 07:39 journal/
-rw-r-----. 1 derekh derekh 120M Sep 24 07:54 journal/
JOBLOGS ]$ wc heat/heat-
302099 3328855 67386843 heat/heat-
JOBLOGS ]$ journalctl --file ./journal/
178398 2854476 49832178
This a far too verbose and as far as I can see most of the log entries are repeating themselves, the quantity of data need to be reduced.
no longer affects: | heat/mitaka |
no longer affects: | heat/liberty |
Changed in heat: | |
status: | In Progress → Fix Committed |
Changed in heat: | |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | liberty-rc2 → 5.0.0 |
I think the issue is we should only ever dump the " Registering foo" data on create or update, only for the parent stack, but I think we're doing it for all nested stacks and/or all other API requests, hence all the duplication.