Back to bug 1381561
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Marius Cornea | 2016-10-04 12:47:27 UTC | CC | mcornea | |
| Zane Bitter | 2016-10-04 13:41:28 UTC | CC | jjoyce, jschluet, slinaber, tvignaud | |
| Component | openstack-heat | puppet-heat | ||
| Link ID | OpenStack gerrit 378639 | |||
| Assignee | zbitter | rhos-maint | ||
| QA Contact | augol | nlevinki | ||
| Zane Bitter | 2016-10-04 13:42:43 UTC | CC | zbitter | |
| Jon Schlueter | 2016-10-04 13:43:53 UTC | Keywords | AutomationBlocker, Triaged | |
| Status | NEW | ON_DEV | ||
| Target Release | --- | 10.0 (Newton) | ||
| Assignee | rhos-maint | jschluet | ||
| Target Milestone | --- | rc | ||
| Jon Schlueter | 2016-10-04 13:47:20 UTC | Status | ON_DEV | MODIFIED |
| Fixed In Version | puppet-heat-9.4.0-1.1.el7ost | |||
| Jon Schlueter | 2016-10-04 15:10:28 UTC | Doc Text | Cause: there were 2 patches required for tripleo to configure yaql memory quota correctly and one of them had not landed yet in a tag Consequence: when attempting certain overcloud deploy scenarios the deploy would fail with 'Expression consumed too much memory' during overcloud deploy Fix: applied upstream patch to puppet-heat to look for the config and apply it Result: overcloud deploy should just work again. | |
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Jon Schlueter | 2016-10-05 02:03:33 UTC | CC | rhos-flags | |
| Flags | needinfo?(rhos-flags) | |||
| Alexandre Maumené | 2016-10-05 07:41:23 UTC | CC | amaumene | |
| Thierry Vignaud | 2016-10-05 07:50:49 UTC | Status | MODIFIED | ON_DEV |
| Marius Cornea | 2016-10-05 07:55:53 UTC | Flags | needinfo?(amaumene) | |
| Thierry Vignaud | 2016-10-05 09:20:48 UTC | Status | ON_DEV | MODIFIED |
| Alexandre Maumené | 2016-10-05 09:22:27 UTC | Flags | needinfo?(rhos-flags) needinfo?(amaumene) | |
| Jaromir Coufal | 2016-10-05 12:27:13 UTC | CC | jcoufal | |
| errata-xmlrpc | 2016-10-06 07:39:18 UTC | Status | MODIFIED | ON_QA |
| nlevinki | 2016-10-06 08:53:55 UTC | QA Contact | nlevinki | augol |
| Jaromir Coufal | 2016-10-13 19:28:49 UTC | Priority | unspecified | medium |
| Amit Ugol | 2016-11-02 06:15:31 UTC | Status | ON_QA | VERIFIED |
| Dan Macpherson | 2016-11-23 04:21:54 UTC | CC | dmacpher | |
| Doc Text | Cause: there were 2 patches required for tripleo to configure yaql memory quota correctly and one of them had not landed yet in a tag Consequence: when attempting certain overcloud deploy scenarios the deploy would fail with 'Expression consumed too much memory' during overcloud deploy Fix: applied upstream patch to puppet-heat to look for the config and apply it Result: overcloud deploy should just work again. | The OpenStack Platform director exceeded the default memory limits for using OpenStack Orchestration (heat) YAQL expressions. This caused an "Expression consumed too much memory" error during an overcloud deployment and subsequent deployment failure. This fix increases the default memory limits for the director, which results in a error-free overcloud deployment. | ||
| errata-xmlrpc | 2016-12-14 13:47:46 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-12-14 16:07:29 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-12-14 11:07:29 UTC |
Back to bug 1381561