Bug 1038538 - openshift-gears service can not be started after upgrade ose from 1.2 to 2.0
Summary: openshift-gears service can not be started after upgrade ose from 1.2 to 2.0
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: 2.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Jason DeTiberus
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-05 09:55 UTC by Johnny Liu
Modified: 2017-03-08 17:35 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-17 16:20:35 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Johnny Liu 2013-12-05 09:55:47 UTC 
Description of problem:
After upgrade ose form 1.2 to 2.0, openshift-gears service can not be started with the following error:
# /etc/init.d/openshift-gears restart
Restarting gear 52980a19f16d95099e0000ac... [ FAILED ]
      Could not determine gear information for: 52980a19f16d95099e0000ac
Restarting gear 529804c8f16d95099e000034... [ FAILED ]
      Could not determine gear information for: 529804c8f16d95099e000034
Restarting gear 52980b24f16d95099e0000e4... [ FAILED ]
      Could not determine gear information for: 52980b24f16d95099e0000e4
Restarting gear 5298071af16d95099e00008d... [ FAILED ]
      Could not determine gear information for: 5298071af16d95099e00008d



Version-Release number of selected component (if applicable):
http://etherpad.corp.redhat.com/ose-2-0-upgrade-2013-12-04

How reproducible:
Always

Steps to Reproduce:
1. Setup ose-1.2 env
2. Create several app on the node.
3. Upgrade env from 1.2 to 2.0
4. Reboot broker and node.
5. Try to access app
6. Try to restart openshift-gears service


Actual results:
Step 5, app is not available
Step 6, fail to restart openshift-gears service.
# /etc/init.d/openshift-gears restart
Restarting gear 52980a19f16d95099e0000ac... [ FAILED ]
      Could not determine gear information for: 52980a19f16d95099e0000ac
Restarting gear 529804c8f16d95099e000034... [ FAILED ]
      Could not determine gear information for: 529804c8f16d95099e000034
Restarting gear 52980b24f16d95099e0000e4... [ FAILED ]
      Could not determine gear information for: 52980b24f16d95099e0000e4
Restarting gear 5298071af16d95099e00008d... [ FAILED ]
      Could not determine gear information for: 5298071af16d95099e00008d


Expected results:
openshift-gears service should be started successfully.

Additional info:
If I use oo-admin-ctl-gears to start one gear, it is working well.
[root@node ~]# oo-admin-ctl-gears restartgear 529fe12cf16d95e42b000010
Restarting gear 529fe12cf16d95e42b000010... [ OK ]
Comment 2 Jason DeTiberus 2013-12-06 00:20:08 UTC 
https://github.com/openshift/enterprise-server/pull/163

Latest pad (http://etherpad.corp.redhat.com/ose-2-0-upgrade-2013-12-05) links to the puddle that contains the updated node package
Comment 3 Johnny Liu 2013-12-06 10:49:55 UTC 
Verify this bug following http://etherpad.corp.redhat.com/ose-2-0-upgrade-2013-12-05, and PASS.
Note You need to log in before you can comment on or make changes to this bug.