Bug 1021041

Summary: Scaled gears are being left behind
Product: OpenShift Online Reporter: Matt Woodson <mwoodson>
Component: PodAssignee: Abhishek Gupta <abhgupta>
Status: CLOSED CURRENTRELEASE QA Contact: libra bugs <libra-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2.xCC: abhgupta, jhou
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-24 03:25:27 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:

Description Matt Woodson 2013-10-18 20:28:13 UTC
Description of problem:

It appears that gears that are part of scaled apps are not being cleaned up when the app is removed.  We are seeing this quite often in our environment, showing up in the accept-node scripts

I am unable to tell if this is broker or node code that needs to be fixed.

This is the error we are seeing in oo-accept-node:

FAIL: directory 5260fc635973ca008d0002dd doesn't have a cartridge directory

Version-Release number of selected component (if applicable):

rhc-node-1.15.4-1.el6oso.x86_64

How reproducible:

Not sure

Steps to Reproduce:

Do not know steps to reproduce, but we have seen this issue quite a bit in our prod online environment.

please follow up with ops team for info on diagnosing this.

Comment 1 Abhishek Gupta 2013-10-18 23:44:44 UTC
Potential fix --> https://github.com/openshift/origin-server/pull/3939

Comment 2 openshift-github-bot 2013-10-22 02:52:27 UTC
Commit pushed to master at https://github.com/openshift/origin-server

https://github.com/openshift/origin-server/commit/fcae2c3d7778d645758352fcdc6a006d95c29e96
Fix for bug 1020440, 1021041, 1021462, 1021467, and a typo

Comment 4 Jianwei Hou 2013-10-23 10:58:37 UTC
Unable to reproduce this issue on devenv-stage_528, not sure how this happened, but everything works fine in today's test. Mark this bug as verified.