Description of problem: When following https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html-single/advanced_overcloud_customization/#sect-Configuring_Containerized_Compute_Nodes Version-Release number of selected component (if applicable): OSP 10 How reproducible: default undercloud deployment, follow https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html-single/advanced_overcloud_customization/#sect-Configuring_Containerized_Compute_Nodes Steps to Reproduce: 1. 2. 3. Actual results: When following https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html-single/advanced_overcloud_customization/#sect-Configuring_Containerized_Compute_Nodes , I hit this: ~~~ u'version': u'2.0'}}, u'message': u"Failed to run action [action_ex_id=f7a8552e-c4fc-44f9-bc3f-9e34428fc947, action_cls='<class 'mistral.actions.action_factory.DeployStackAction'>', attributes='{}', params='{u'container': u'overcloud', u'timeout': 240}']\n ERROR: Failed to validate: : resources.ControllerServiceChain: : Failed to validate: resources.PuppetServices: Failed to validate nested template: Failed to validate: resources[7]: Failed to validate: resources.CinderVolumeBase: Failed to validate: resources.CinderBase: Request limit exceeded: Recursion depth exceeds 5.", ~~~ I'm using pretty much stock templates now, with ~~~ openstack overcloud deploy --templates \ -e /usr/share/openstack-tripleo-heat-templates/environments/docker.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/docker-network.yaml \ --control-flavor control --compute-flavor compute --ceph-storage-flavor ceph-storage \ --control-scale $control_scale --compute-scale $compute_scale --ceph-storage-scale $ceph_scale \ --ntp-server $ntpserver \ --neutron-network-type vxlan --neutron-tunnel-types vxlan ~~~ Expected results: Additional info: This can be fixed by setting increasing the maximum stack depth in /etc/heat/heat.conf [root@undercloud-4 ~]# grep depth /etc/heat/* grep: /etc/heat/environment.d: Is a directory /etc/heat/heat.conf:# Maximum depth allowed when using nested stacks. (integer value) /etc/heat/heat.conf:max_nested_stack_depth = 10 grep: /etc/heat/templates: Is a directory [root@undercloud-4 ~]# grep depth /etc/mistral/* -R [root@undercloud-4 ~]# grep depth /etc/zaqar/* -R We need to update the documentation to instruct users to do this. Thanks, Andreas
I got this issue too when trying a containerized compute deployment in OSP10. In addition to the modification to the /etc/heat/heat.conf file, I needed to run the following command to make the change active : sudo systemctl restart openstack-heat-engine.service
I don't think documenting a workaround is suitable for this issue. I say this because even if you manually change the value and restart the service, the value will get reverted when you perform an minor update or major upgrade of the undercloud. This is because the value is set via the heat::engine::max_nested_stack_depth hieradata. It might be a good idea to reassign this bug as an engineering bug.
Andreas, have you already got an engineering BZ open for this issue?
Emilien, what's your assessment of this BZ? Would it be better to implement a fix in instack-undercloud?
As a temporary measure, I've included some documentation on the issue: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html-single/advanced_overcloud_customization/#sect-Increasing_the_Stack_Depth However, I really think this is more suited to an engineering fix. Emilien, what did you want to do?
I think we already did it in https://review.openstack.org/#/c/397508/ but the code is probably not in Newton. Steve, do you think we should backport it?
*** This bug has been marked as a duplicate of bug 1447111 ***