Bug 1218049
Summary: | Failed to repair the HA app with the head gear located on the unresponsive node | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Evgheni Dereveanchin <ederevea> |
Component: | Node | Assignee: | Timothy Williams <tiwillia> |
Status: | CLOSED ERRATA | QA Contact: | libra bugs <libra-bugs> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 2.2.0 | CC: | abhgupta, adellape, asogukpi, bleanhar, bmeng, cryan, ederevea, erich, jialiu, jokerman, libra-bugs, libra-onpremise-devel, mmccomas, nicholas_schuetz, pep, tiwillia, xiama |
Target Milestone: | --- | Keywords: | NeedsTestCase, UpcomingRelease |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openshift-origin-broker-util-1.35.2.3-1 | Doc Type: | Bug Fix |
Doc Text: |
Previously, when a node containing a head gear for a scaled application was lost and the gear could not be recovered, running the oo-admin-repair tool still attempted to recover the gear. The tool then reported an error and the gear was not recovered, but changes were made to the broker's database. As a result, running the tool again reported all gears had been recovered, even though the head gear still did not exist. This bug fix updates oo-admin-repair to distinguish applications with lost head gears from regular lost gears from scaled applications. The tool now offers to delete any applications with lost head gears, informing the administrator to first re-create such applications from source or recent backups and move any existing alias before proceeding.
|
Story Points: | --- |
Clone Of: | 1102557 | Environment: | |
Last Closed: | 2015-07-21 19:12:40 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1102557 | ||
Bug Blocks: |
Comment 1
Evgheni Dereveanchin
2015-05-04 06:30:52 UTC
Commit pushed to master at https://github.com/openshift/origin-server https://github.com/openshift/origin-server/commit/71f7ade01db3f830f5aae3480095932e62584d83 oo-admin-repair should properly handle HA apps with deleted head gears Bug 1218049 Bugzilla Link https://bugzilla.redhat.com/show_bug.cgi?id=1218049 oo-admin-repair previously attempted to resolve HA applications with missing head gears as though they were simply missing a web-proxy gear. When a head gear is missing, the application cannot be recovered. oo-admin-repair should offer to cleanly remove the application rather than attempt to fix it (and break it more in the process). Check on puddle [2.2.6/2015-05-18.1] 1. create an app # rhc app create xiaomn1 php-5.4 -s 2. enable ha for the app # rhc app enable-ha xiaomn1 3. find the node which the head gear is on, and stop it # /etc/init.d/ruby193-mcollective stop 4. repair node in broker # oo-admin-repair --removed-nodes Started at: 2015-05-19 08:47:36 UTC Total gears found in mongo: 4 Servers that are unresponsive: Server: node1.ose22-auto.com.cn (district: default-small), Confirm [yes/no]: yes Some servers are unresponsive: node1.ose22-auto.com.cn Found 1 HA applications that cannot be recovered due to missing head gear. xiaomn1 (id: 555af7af82611d7870000001) These apps should be re-created and any existing aliases moved for recovery before deletion. Do you want to delete all of them now [yes/no]: yes Do you want to delete unresponsive servers from their respective districts [yes/no]: yes Finished at: 2015-05-19 08:48:10 UTC Total time: 33.561s SUCCESS The node is removed from env. Commit pushed to master at https://github.com/openshift/origin-server https://github.com/openshift/origin-server/commit/60abe78eecdcd9cd029864fbc2af04d71eca1888 Test incorrectly expects less usage records Bug 1218049 A test modified for bz 1218049 incorrectly expects a certain number of usage records for a test. The test creates an additional gear that was not previously accounted for. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-1463.html |