Bug 1032484 - ~/haproxy/conf/gear-registry.db does not get created during scale-up
~/haproxy/conf/gear-registry.db does not get created during scale-up
Status: CLOSED NOTABUG
Product: OpenShift Online
Classification: Red Hat
Component: Pod (Show other bugs)
1.x
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Abhishek Gupta
libra bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-20 04:46 EST by Oleg Fayans
Modified: 2016-11-30 19:27 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-11-20 05:01:26 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Oleg Fayans 2013-11-20 04:46:09 EST
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.