Back to bug 1025048
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Luke Meyer | 2013-10-30 20:43:22 UTC | Status | NEW | MODIFIED |
| Luke Meyer | 2013-10-31 14:17:51 UTC | Status | MODIFIED | ON_QA |
| Fixed In Version | openshift-origin-broker-util-1.9.15-1 | |||
| Doc Text | Feature: Adds a report for the following situation: a) User adds a gear to a node b) Admin changes the hostname of the node, making the app essentially inaccessible by the user via broker and causing loads of other problems. While looking through all gears the nodes report, this now checks that the node hostname matches what is in the DB for the gear. This could briefly give spurious failures if a gear is being moved at the time, but should otherwise be considered a legitimate problem. Reason: Actual customers have done this and debugging the problem is really difficult without this. Also if someone has done this, an upgrade will fail (hang trying to contact gears). Result (if any): It's at least possible to detect the problem easily with oo-admin-chk. | |||
| Doc Type | Bug Fix | Enhancement | ||
| Luke Meyer | 2013-10-31 16:00:15 UTC | Target Release | --- | 1.2.5 |
| Version | 1.2.1 | 1.0.0 | ||
| Ma xiaoqiang | 2013-11-04 06:57:29 UTC | Status | ON_QA | VERIFIED |
| CC | xiama | |||
| Brenton Leanhardt | 2013-11-23 14:50:45 UTC | Target Release | 1.2.5 | 1.2.7 |
| Brenton Leanhardt | 2013-12-16 06:07:56 UTC | CC | bleanhar | |
| Xiaoli Tian | 2013-12-16 06:11:02 UTC | CC | xtian | |
| Alex Dellapenta | 2014-01-09 21:12:09 UTC | CC | adellape | |
| Doc Text | Feature: Adds a report for the following situation: a) User adds a gear to a node b) Admin changes the hostname of the node, making the app essentially inaccessible by the user via broker and causing loads of other problems. While looking through all gears the nodes report, this now checks that the node hostname matches what is in the DB for the gear. This could briefly give spurious failures if a gear is being moved at the time, but should otherwise be considered a legitimate problem. Reason: Actual customers have done this and debugging the problem is really difficult without this. Also if someone has done this, an upgrade will fail (hang trying to contact gears). Result (if any): It's at least possible to detect the problem easily with oo-admin-chk. | If the hostname of a node host changes after its initial setup, applications with existing gears on that node host can become inaccessible to an OpenShift Enterprise user. Many other problems can result as well. To help detect this issue, the oo-admin-chk command now checks whether the current hostname of a reporting node host matches what is recorded in the datastore for any gear discovered on that node host. This may briefly report problems if a gear is being moved at the time the command is run, but should otherwise be considered a legitimate issue. Detecting and correcting this issue also helps prevent future upgrade problems. | ||
| errata-xmlrpc | 2014-01-10 13:02:19 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2014-01-13 15:06:34 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2014-01-13 10:06:34 UTC | |||
| Dan McPherson | 2017-03-08 17:35:34 UTC | Target Release | 1.2.7 |
Back to bug 1025048