Set max_resources_per_stack to -1 The max_resources_per_stack configuration option for Heat engine is meant to prevent DOS attacks by large stacks. For TripleO, the check itself is actually quite resource instensive since it takes a while to actually count the resources in all the nested stacks. The tenant in the undercloud is trusted anyway. Setting the option to -1 disables the check and makes a significant improvement in overcloud deployment time.
FailedQA Environment:instack-undercloud-2.2.5-1.el7ost.noarch grep max_resources_per_stack /etc/heat/heat.conf #max_resources_per_stack = 1000
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10.
Verified: Environment: instack-undercloud-5.1.0-4.el7ost.noarch [stack@undercloud-0 ~]$ sudo grep max_resources_per_stack /etc/heat/heat.conf #max_resources_per_stack = 1000 max_resources_per_stack = -1
According to our records, this should be resolved by instack-undercloud-5.1.0-4.el7ost. This build is available now.