Description of problem: With current 2016-10-04.1 snapshot, we got the above error from heat when we try to deploy the overcloud. 11:37:48 stdout: 2016-10-04 11:37:38Z [42]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:38Z [69]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:38Z [46]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:38Z [29]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:38Z [41]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:38Z [8]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:38Z [68]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:38Z [64]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:38Z [30]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:38Z [35]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:38Z [11]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:38Z [36]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:38Z [54]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:38Z [13]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:38Z [18]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:38Z [26]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:38Z [14]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [55]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [15]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [67]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [31]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [0]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [10]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [5]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [4]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [12]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [19]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [71]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [40]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [16]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [57]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [7]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [1]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [51]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [44]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [33]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [45]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [61]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [63]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [60]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [2]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [20]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [70]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [23]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [34]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [50]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [6]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [47]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [43]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [38]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [59]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [9]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:39Z [overcloud-ControllerServiceChain-3ngdcv5gekmz-ServiceChain-tf67457ua6cu]: CREATE_COMPLETE Stack CREATE completed successfully 11:37:48 2016-10-04 11:37:40Z [ServiceChain]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:40Z [overcloud-ControllerServiceChain-3ngdcv5gekmz]: CREATE_COMPLETE Stack CREATE completed successfully 11:37:48 2016-10-04 11:37:40Z [ControllerServiceChain]: CREATE_COMPLETE state changed 11:37:48 2016-10-04 11:37:46Z [overcloud]: CREATE_FAILED Resource CREATE failed: Expression consumed too much memory 11:37:48 11:37:48 Stack overcloud CREATE_FAILED The host is el7.3 beta, and it is our usual 1 cpu, 1 cnt, 1 ceph setup. List of packages: https://paste.fedoraproject.org/443155/47558504/ The 'Expression consumed too much memory' string found in the 'yaql' library, we expected to have change merged which increased the memory limit. The heat-engine log also has 'Expression consumed too much memory' string, but without any detail.
Our version expected to be new enough to have this change: https://github.com/openstack/instack-undercloud/commit/55ccd0e1e8c66c9f474112358063bc263720d84f (not verifed)
(In reply to Attila Fazekas from comment #2) > Our version expected to be new enough to have this change: > https://github.com/openstack/instack-undercloud/commit/ > 55ccd0e1e8c66c9f474112358063bc263720d84f (not verifed) The fix appears to be there but the error still shows up. I hit it with 1 controller + 1 compute: grep heat::yaql_memory_quota /usr/share/instack-undercloud/puppet-stack-config/puppet-stack-config.yaml.template heat::yaql_memory_quota: 100000 instack-undercloud.noarch 5.0.0-0.20160929132429.56e65af.el7ost
I gather that y'all have this instack-undercloud change: https://review.openstack.org/377782 but are probably missing the corresponding puppet-heat change: https://review.openstack.org/378639
(In reply to Zane Bitter from comment #4) > I gather that y'all have this instack-undercloud change: > > https://review.openstack.org/377782 > > but are probably missing the corresponding puppet-heat change: > > https://review.openstack.org/378639 yep that's it, working on build for it.
Hi, With: puppet-heat-9.4.0-1.1.el7ost.noarch instack-undercloud-5.0.0-0.20160929132429.56e65af.el7ost.noarch Result is still: 2016-10-05 07:36:38Z [overcloud-ControllerServiceChain-36ecvlqvrx3t-ServiceChain-jbopffivvg74]: CREATE_COMPLETE Stack CREATE completed successfully 2016-10-05 07:36:39Z [ServiceChain]: CREATE_COMPLETE state changed 2016-10-05 07:36:39Z [overcloud-ControllerServiceChain-36ecvlqvrx3t]: CREATE_COMPLETE Stack CREATE completed successfully 2016-10-05 07:36:39Z [ControllerServiceChain]: CREATE_COMPLETE state changed 2016-10-05 07:36:49Z [CephStorage]: CREATE_IN_PROGRESS state changed 2016-10-05 07:36:49Z [Compute]: CREATE_IN_PROGRESS state changed 2016-10-05 07:36:51Z [overcloud-Compute-agk5lybjxlmz]: CREATE_IN_PROGRESS Stack CREATE started 2016-10-05 07:36:51Z [ObjectStorage]: CREATE_IN_PROGRESS state changed 2016-10-05 07:36:51Z [1]: CREATE_IN_PROGRESS state changed 2016-10-05 07:36:52Z [CephStorage]: CREATE_FAILED CREATE aborted 2016-10-05 07:36:52Z [Compute]: CREATE_FAILED CREATE aborted 2016-10-05 07:36:52Z [ObjectStorage]: CREATE_FAILED CREATE aborted 2016-10-05 07:36:52Z [overcloud]: CREATE_FAILED Resource CREATE failed: Expression consumed too much memory 2016-10-05 07:36:54Z [0]: CREATE_IN_PROGRESS state changed 2016-10-05 07:36:54Z [overcloud-Compute-agk5lybjxlmz-1-e6nmqr4svmv7]: CREATE_IN_PROGRESS Stack CREATE started 2016-10-05 07:36:54Z [NodeAdminUserData]: CREATE_IN_PROGRESS state changed 2016-10-05 07:36:54Z [UpdateConfig]: CREATE_IN_PROGRESS state changed 2016-10-05 07:36:55Z [NodeUserData]: CREATE_IN_PROGRESS state changed Stack overcloud CREATE_FAILED Heat Stack create failed.
Moving back to dev stage then
(In reply to Alexandre Maumené from comment #6) > Hi, > > With: > puppet-heat-9.4.0-1.1.el7ost.noarch > instack-undercloud-5.0.0-0.20160929132429.56e65af.el7ost.noarch > > Result is still: > 2016-10-05 07:36:38Z > [overcloud-ControllerServiceChain-36ecvlqvrx3t-ServiceChain-jbopffivvg74]: > CREATE_COMPLETE Stack CREATE completed successfully > 2016-10-05 07:36:39Z [ServiceChain]: CREATE_COMPLETE state changed > 2016-10-05 07:36:39Z [overcloud-ControllerServiceChain-36ecvlqvrx3t]: > CREATE_COMPLETE Stack CREATE completed successfully > 2016-10-05 07:36:39Z [ControllerServiceChain]: CREATE_COMPLETE state changed > 2016-10-05 07:36:49Z [CephStorage]: CREATE_IN_PROGRESS state changed > 2016-10-05 07:36:49Z [Compute]: CREATE_IN_PROGRESS state changed > 2016-10-05 07:36:51Z [overcloud-Compute-agk5lybjxlmz]: CREATE_IN_PROGRESS > Stack CREATE started > 2016-10-05 07:36:51Z [ObjectStorage]: CREATE_IN_PROGRESS state changed > 2016-10-05 07:36:51Z [1]: CREATE_IN_PROGRESS state changed > 2016-10-05 07:36:52Z [CephStorage]: CREATE_FAILED CREATE aborted > 2016-10-05 07:36:52Z [Compute]: CREATE_FAILED CREATE aborted > 2016-10-05 07:36:52Z [ObjectStorage]: CREATE_FAILED CREATE aborted > 2016-10-05 07:36:52Z [overcloud]: CREATE_FAILED Resource CREATE failed: > Expression consumed too much memory > 2016-10-05 07:36:54Z [0]: CREATE_IN_PROGRESS state changed > 2016-10-05 07:36:54Z [overcloud-Compute-agk5lybjxlmz-1-e6nmqr4svmv7]: > CREATE_IN_PROGRESS Stack CREATE started > 2016-10-05 07:36:54Z [NodeAdminUserData]: CREATE_IN_PROGRESS state changed > 2016-10-05 07:36:54Z [UpdateConfig]: CREATE_IN_PROGRESS state changed > 2016-10-05 07:36:55Z [NodeUserData]: CREATE_IN_PROGRESS state changed > > Stack overcloud CREATE_FAILED > > Heat Stack create failed. Do you get the 'Expression consumed too much memory' message in the FAIL step? This BZ was targeting this particular error. If there's another issue we should open a different BZ for it.
Ok I think I posted to quickly... I didn't run "openstack undercloud install" to update the parameters in /etc/heat/heat.conf after updating the packages. It should be fixed and I'm testing it atm. I'll update this BZ to confirm.
Moving back to MODIFIED then
I confirm that I'm not hitting this issue any more after updating the packages. Thanks.
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