Bug 1032484 - ~/haproxy/conf/gear-registry.db does not get created during scale-up
Summary: ~/haproxy/conf/gear-registry.db does not get created during scale-up
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Pod
Version: 1.x
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Abhishek Gupta
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-20 09:46 UTC by Oleg Fayans
Modified: 2016-12-01 00:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-20 10:01:26 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Oleg Fayans 2013-11-20 09:46:09 UTC 
Description of problem:

During the scale-up of the app the following file should be created:
~/haproxy/conf/gear-registry.db
But it does not

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

How reproducible:
Always

Steps to Reproduce:
1. Create a scalable app
2. Scale it up
3. ssh to the head gear, navigate to haproxy/conf/ filder and issue the "ls" command

Actual results:
haproxy.cfg  haproxy.cfg.lock

Expected results:
haproxy.cfg  haproxy.cfg.lock gear-registry.db

Additional info:
Note You need to log in before you can comment on or make changes to this bug.