Bug 1395740
Summary: | Overcloud stack with a large number of nodes fails with: Resource CREATE failed: Collection length exceeds 200 elements | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Marius Cornea <mcornea> |
Component: | instack-undercloud | Assignee: | Steven Hardy <shardy> |
Status: | CLOSED ERRATA | QA Contact: | Marius Cornea <mcornea> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 10.0 (Newton) | CC: | dbecker, jschluet, jslagle, mburns, morazi, rhel-osp-director-maint, shardy |
Target Milestone: | ga | Keywords: | Triaged |
Target Release: | 10.0 (Newton) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | instack-undercloud-5.1.0-3.el7ost | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-12-14 16:33:02 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Marius Cornea
2016-11-16 14:55:46 UTC
The problem is we're missing a fix that increases the yaql limit_iterators in the heat.conf on the undercloud (from the default of 200, which is too small for the large stacks we're creating with TripleO in this case). Upstream bug raised, and backport proposed: https://bugs.launchpad.net/tripleo/+bug/1642287 https://review.openstack.org/#/c/398396/ Workaround: 1. Create hieradata file: cat /home/stack/custom_hiera.yaml heat::yaql_limit_iterators: 1000 2. Edit undercloud.conf and point it to the hieradata file hieradata_override = /home/stack/custom_hiera.yaml 3. Rerun openstack undercloud install https://review.openstack.org/#/c/398396/ landed, verfied by inspection it's included in instack-undercloud-5.1.0-3.el7ost.noarch.rpm Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-2948.html |