Back to bug 1027122
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Brenton Leanhardt | 2013-11-14 15:38:29 UTC | Status | NEW | ASSIGNED |
| CC | bleanhar | |||
| Assignee | lmeyer | jdetiber | ||
| Brenton Leanhardt | 2013-11-15 21:44:37 UTC | Target Release | --- | 2.0 |
| Brenton Leanhardt | 2013-11-22 17:18:27 UTC | CC | twoerner | |
| Brenton Leanhardt | 2013-11-22 18:54:14 UTC | Target Release | 2.0 | 2.0.1 |
| CC | erich | |||
| Depends On | 1032798 | |||
| manoj | 2013-12-05 15:15:57 UTC | Assignee | jdetiber | bleanhar |
| Alex Dellapenta | 2013-12-05 22:51:28 UTC | Blocks | 1038831 | |
| Brenton Leanhardt | 2014-01-06 17:12:54 UTC | Target Release | 2.0.1 | 2.0.2 |
| Brenton Leanhardt | 2014-01-08 15:39:15 UTC | Target Release | 2.0.2 | 2.0.3 |
| patrick | 2014-01-09 21:19:10 UTC | CC | pch | |
| Brenton Leanhardt | 2014-01-29 17:07:21 UTC | Status | ASSIGNED | MODIFIED |
| CC | jolamb | |||
| errata-xmlrpc | 2014-01-30 20:48:23 UTC | Status | MODIFIED | ON_QA |
| John W. Lamb | 2014-01-30 21:14:41 UTC | Fixed In Version | rubygem-openshift-origin-node-1.17.5.8-1 rubygem-openshift-origin-common-1.17.2.7-1 | |
| Peter Ruan | 2014-01-31 07:56:20 UTC | Status | ON_QA | VERIFIED |
| CC | pruan | |||
| John W. Lamb | 2014-02-11 16:16:06 UTC | Doc Text | Cause: Lokkit removes critical OpenShift iptables rules Consequence: Using lokkit results in node outages because critical iptables rules are flushed Fix: oo-diagnostics has been updated to detect if lokkit or system-config-firewall are in use, and to advise the user against the use of lokkit. In the event that the user requires the user of lokkit, oo-diagnostics also provides a snippet that can be added to the user's lokkit configuration to allow interoperation with OpenShift. Result: Outages due to conflicting iptables configurations should be reduced. |
|
| Alex Dellapenta | 2014-02-18 20:43:10 UTC | CC | adellape | |
| Doc Text | Cause: Lokkit removes critical OpenShift iptables rules Consequence: Using lokkit results in node outages because critical iptables rules are flushed Fix: oo-diagnostics has been updated to detect if lokkit or system-config-firewall are in use, and to advise the user against the use of lokkit. In the event that the user requires the user of lokkit, oo-diagnostics also provides a snippet that can be added to the user's lokkit configuration to allow interoperation with OpenShift. Result: Outages due to conflicting iptables configurations should be reduced. | The lokkit tool removed critical iptables rules required by OpenShift Enterprise, resulting in node outages. This bug fix updates the oo-diagnostics tool to detect if the lokkit or system-config-firewall tools are used, and advises the user not to use lokkit. If lokkit is required by the user, oo-diagnostics also provides a snippet that users can add to their lokkit configuration to allow interoperation with OpenShift Enterprise. Outages due to conflicting iptables configurations are now reduced. | ||
| errata-xmlrpc | 2014-02-21 11:00:37 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2014-02-25 15:41:14 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2014-02-25 10:41:14 UTC | |||
| Dan McPherson | 2017-03-08 17:36:08 UTC | Target Release | 2.0.3 |
Back to bug 1027122