Back to bug 1032798

Who When What Removed Added
Brenton Leanhardt 2013-11-22 18:54:14 UTC Blocks 1027122
Alex Dellapenta 2013-12-05 22:51:28 UTC Blocks 1038831
Brenton Leanhardt 2014-01-06 17:11:37 UTC Target Release --- 2.0.2
Brenton Leanhardt 2014-01-08 20:51:11 UTC Status NEW ASSIGNED
Brenton Leanhardt 2014-01-09 19:07:51 UTC CC saurap
Flags needinfo?(saurap)
saurabh sharma 2014-01-09 23:12:38 UTC Flags needinfo?(saurap)
Nikhil Mone 2014-01-13 13:59:37 UTC CC nmone
Miciah Dashiel Butler Masters 2014-01-14 23:44:06 UTC CC mmasters
Brenton Leanhardt 2014-01-17 16:06:58 UTC Target Release 2.0.2 2.0.3
Brenton Leanhardt 2014-01-29 17:06:08 UTC Status ASSIGNED MODIFIED
John W. Lamb 2014-01-30 20:34:25 UTC CC jolamb
Chris Ryan 2014-01-30 20:55:22 UTC CC cryan
John W. Lamb 2014-01-30 21:14:44 UTC Fixed In Version rubygem-openshift-origin-node-1.17.5.8-1 rubygem-openshift-origin-common-1.17.2.7-1
errata-xmlrpc 2014-01-30 21:31:06 UTC Status MODIFIED ON_QA
Peter Ruan 2014-01-31 08:19:45 UTC Status ON_QA VERIFIED
CC pruan
John Wiebalk 2014-02-03 16:06:23 UTC CC wiebjr
John W. Lamb 2014-02-11 15:43:57 UTC Doc Text Cause:
Node tries to insert an iptables rule without first verifying that the target table exists
Consequence:
Scaled app creation would fail on nodes where no iptables rules are defined
Fix:
oo-diagnostics now checks for missing iptables rules. oo-admin-ctl-uptables-port-proxy has been updated to guarantee the expected iptables tables exist prior to modifying and to emit useful warnings when the table is found to be missing in the running configuration.
Result:
Alex Dellapenta 2014-02-18 22:21:15 UTC CC adellape
Doc Text Cause:
Node tries to insert an iptables rule without first verifying that the target table exists
Consequence:
Scaled app creation would fail on nodes where no iptables rules are defined
Fix:
oo-diagnostics now checks for missing iptables rules. oo-admin-ctl-uptables-port-proxy has been updated to guarantee the expected iptables tables exist prior to modifying and to emit useful warnings when the table is found to be missing in the running configuration.
Result:
Previously, when a node host attempted to insert an iptables rule without first verifying that the target table existed, a scalable application could not be created where iptables rules were not defined. This bug fix adds logic to the oo-diagnostics tool to check for missing iptables rules. The oo-admin-ctl-iptables-port-proxy tool has been updated to confirm that the expected tables exist before modifying them, and to provide useful warning messages when the table is missing in the active configuration.
errata-xmlrpc 2014-02-21 11:02:51 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2014-02-25 15:41:22 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2014-02-25 10:41:22 UTC
Johnny Liu 2014-02-26 07:58:49 UTC CC jialiu
Dan McPherson 2017-03-08 17:36:08 UTC Target Release 2.0.3

Back to bug 1032798