Back to bug 1002919
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Johnny Liu | 2013-08-30 09:14:40 UTC | Summary | scalable app fail to be restart | scalable app fail to be restart after upgrade |
| Johnny Liu | 2013-08-30 09:19:08 UTC | Summary | scalable app fail to be restart after upgrade | scalable app fail to be restarted after upgrade |
| Brenton Leanhardt | 2013-08-30 13:15:41 UTC | Target Release | --- | 1.2.2 |
| CC | bleanhar | |||
| Brenton Leanhardt | 2013-08-30 19:18:49 UTC | Status | NEW | ASSIGNED |
| Assignee | lmeyer | bleanhar | ||
| Brenton Leanhardt | 2013-09-02 19:32:42 UTC | Target Release | 1.2.2 | 1.2.3 |
| Brenton Leanhardt | 2013-09-11 14:42:46 UTC | Status | ASSIGNED | MODIFIED |
| Brenton Leanhardt | 2013-09-11 20:22:10 UTC | Status | MODIFIED | ON_QA |
| Fixed In Version | rubygem-openshift-origin-controller-1.9.16.2-1 | |||
| Johnny Liu | 2013-09-13 05:43:24 UTC | Status | ON_QA | VERIFIED |
| Brenton Leanhardt | 2013-09-16 19:37:04 UTC | Doc Text | Cause: Previously the assumption was the that web_proxy gear would always be the first gear in the Gear group. However, in rare cases this would not be the case after the 1.1->1.2 upgrade. Consequence: application restarts would not work. Fix: Backported a patch to make remove the proxy gear ordering assumptions. Result: |
|
| Bilhar | 2013-09-19 03:04:46 UTC | CC | baulakh | |
| Doc Text | Cause: Previously the assumption was the that web_proxy gear would always be the first gear in the Gear group. However, in rare cases this would not be the case after the 1.1->1.2 upgrade. Consequence: application restarts would not work. Fix: Backported a patch to make remove the proxy gear ordering assumptions. Result: | Some applications failed to restart after upgrading from OpenShift Enterprise 1.1 to 1.2 because the web_proxy gear was not always the first gear in a gear goup. This issue has been fixed in the current release of OpenShift Enterprise. | ||
| Bilhar | 2013-09-19 05:55:06 UTC | Doc Text | Some applications failed to restart after upgrading from OpenShift Enterprise 1.1 to 1.2 because the web_proxy gear was not always the first gear in a gear goup. This issue has been fixed in the current release of OpenShift Enterprise. | Some applications failed to restart after upgrading from OpenShift Enterprise 1.1 to 1.2 because the web_proxy gear was not always the first gear in a gear group. This issue has been fixed in the current release of OpenShift Enterprise. |
| Bilhar | 2013-09-20 00:54:24 UTC | Doc Text | Some applications failed to restart after upgrading from OpenShift Enterprise 1.1 to 1.2 because the web_proxy gear was not always the first gear in a gear group. This issue has been fixed in the current release of OpenShift Enterprise. | Some applications failed to restart after upgrading from OpenShift Enterprise 1.1 to 1.2 because the web_proxy gear was not always the first gear in a gear goup. This has been fixed and applications now restart correctly when upgrading OpenShift Enterprise. |
| Bilhar | 2013-09-23 00:25:54 UTC | Doc Text | Some applications failed to restart after upgrading from OpenShift Enterprise 1.1 to 1.2 because the web_proxy gear was not always the first gear in a gear goup. This has been fixed and applications now restart correctly when upgrading OpenShift Enterprise. | Some applications failed to restart after upgrading from OpenShift Enterprise 1.1 to 1.2 because the web_proxy gear was not always the first gear in a gear group. This has been fixed and applications now restart correctly when upgrading OpenShift Enterprise. |
| errata-xmlrpc | 2013-09-25 12:03:26 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2013-09-25 15:30:52 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2013-09-25 11:30:52 UTC | |||
| Dan McPherson | 2017-03-08 17:35:18 UTC | Target Release | 1.2.3 |
Back to bug 1002919