Bug 1005023

Summary:	Jenkins build make haproxy process restart when hot_deploy marker is enabled
Product:	OpenShift Online	Reporter:	chunchen <chunchen>
Component:	Containers	Assignee:	Mrunal Patel <mpatel>
Status:	CLOSED NOTABUG	QA Contact:	libra bugs <libra-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.x	CC:	wsun
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:	2013-09-09 15:11:23 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:

Description chunchen 2013-09-06 04:21:45 UTC

Description of problem:
When deploying a scalable app with hot_deploy marker by jenkins, the haproxy process will be restarted, but it will not restart when building without jenkins.

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

How reproducible:
always

Steps to Reproduce:
1. Create a scalable app with jenkins
rhc app create cpy27s0 python-2.7 -s --enable-jenkins
2. Check the PID of haproxy process
rhc ssh cpy27s0 'ps -ef |grep -w haproxy | grep -v grep'
3. Add hot_deploy marker and push
cd cpy27s0
touch .openshift/markers/hot_deploy
git add .; git commit -amp; git push
4. Check the PID of haproxy process again
rhc ssh cpy27s0 'ps -ef |grep -w haproxy | grep -v grep'

Actual results:
The PID of haproxy process is different at step 2 and step 4

Expected results:
The haproxy process should not be restarted after jenkins build

Additional info:

Comment 1 Mrunal Patel 2013-09-06 18:26:09 UTC

I was unable to reproduce the issue on latest devenv? Could you please retest?

Comment 2 chunchen 2013-09-09 06:48:18 UTC

@ Mrunal Patel 
I tried this issue on devenv_3758,also can not reproduce it now.

Comment 3 Mrunal Patel 2013-09-09 15:11:23 UTC

@chuchen,
I am closing this bug for now. Please re-open or create a new one if we see the issue again.

Thanks,
Mrunal