Back to bug 1470394
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Scott Dodson | 2017-07-13 00:53:23 UTC | Status | NEW | MODIFIED |
| Scott Dodson | 2017-07-13 00:53:45 UTC | Target Release | --- | 3.5.1 |
| Jeff Cantrill | 2017-07-14 14:23:18 UTC | Assignee | jcantril | ejacobs |
| Scott Dodson | 2017-07-17 13:36:09 UTC | Doc Text | Previously the installer created the logging deployment with a non null node selector if a node selector was not provided. This meant that logging would fail to deploy in those scenarios. Now if a node selector is not provided then the deployment uses a null node selector ensuring proper deployment. | |
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Scott Dodson | 2017-07-17 13:36:39 UTC | Assignee | ejacobs | jcantril |
| Erik M Jacobs | 2017-07-17 14:01:24 UTC | Doc Text | Previously the installer created the logging deployment with a non null node selector if a node selector was not provided. This meant that logging would fail to deploy in those scenarios. Now if a node selector is not provided then the deployment uses a null node selector ensuring proper deployment. | The installer handles both installation/configuration of logging during the initial deployment, as well as post-deployment by calling one of the ad-hoc playbooks. In the case where a default project nodeselector was used for the initial installation, the ad-hoc logging deployment would fail due to selector conflicts. Now, the logging project is force created with a null nodeselector to avoid conflicts regardless of when the logging deployment is performed. |
| errata-xmlrpc | 2017-07-24 14:24:42 UTC | Status | MODIFIED | ON_QA |
| Xia Zhao | 2017-07-25 08:33:10 UTC | Status | ON_QA | VERIFIED |
| errata-xmlrpc | 2017-08-30 18:21:06 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2017-08-31 17:00:23 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2017-08-31 13:00:23 UTC |
Back to bug 1470394