Comment 33 for bug 1626675

Using heat master including the recent memory improvements, I've just bisected tripleo-heat-templates down to changes which merged around August 25th - newer changes get OOMed, older changes get stalled with puppet at step 4 but this is usually when the OOM kicks in anyway.

There is nothing suspicious looking merging around the 25th, either side of this change[1] could be investigated.

It could be that the bisect shows gradual memory growth over the changes, and the 25th is when the threshold is reached. I've captured memory use logs for each run so my next step is to graph these and see if there is a trend. tripleo-heat-templates 5.0.0.0b2 looks like a low memory-using baseline.

[1] http://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=b61f1a33d55a23df7cd451679ee356d12c7f4a24