Back to bug 1304935
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| RHEL Program Management | 2016-02-05 01:55:09 UTC | Keywords | ZStream | |
| Zane Bitter | 2016-02-05 02:24:01 UTC | Status | NEW | POST |
| Zane Bitter | 2016-02-11 19:54:26 UTC | Status | POST | MODIFIED |
| Fixed In Version | openstack-heat-2015.1.2-9.el7ost | |||
| errata-xmlrpc | 2016-02-12 17:08:15 UTC | Status | MODIFIED | ON_QA |
| Amit Ugol | 2016-02-16 10:53:05 UTC | CC | zbitter | |
| Flags | needinfo?(zbitter) | |||
| Zane Bitter | 2016-02-16 15:45:06 UTC | Flags | needinfo?(zbitter) | |
| Amit Ugol | 2016-02-17 04:00:03 UTC | Status | ON_QA | VERIFIED |
| Suyog Sainkar | 2016-02-17 07:18:29 UTC | CC | ssainkar | |
| Doc Text | Previously, every time Heat loaded a stack - including just to get the metadata of a resource because os-collect-config is polling it - it logged at INFO level every single type mapping in the user's environment. For TripleO, in particular, there were many such mappings in the standard environment. A typical deployment of TripleO generated several Gigabytes of logs. This patch reduces the frequency of logging environment resources by logging all environment resources (e.g those from resource plugins and the global environment) only when starting the service, and logging user-provided template resources when validating template on create/update, for only the root stack, because this passes a derived subset environment down to all children. This update also switches to using the string representation of the ResourceInfo objects, as this contains more useful information than the previous log format. |
|||
| errata-xmlrpc | 2016-02-18 15:49:08 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-02-18 16:43:35 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-02-18 11:43:35 UTC | |||
| Perry Myers | 2016-04-26 20:04:28 UTC | CC | pmyers | |
| Red Hat One Jira (issues.redhat.com) | 2022-07-09 08:19:54 UTC | Link ID | Red Hat Issue Tracker OSP-16753 |
Back to bug 1304935