Red Hat Bugzilla – Bug 826447
scaled-up gear infomation will not be added to gear-registry.db for scalable app with mongodb/mysql embedded
Last modified: 2015-05-14 18:54:43 EDT
Description of problem:
scale-up scalable app with mongodb/mysql embedded, check /haproxy-status/ page for gear infomation, will not find the new added gear, and ssh login to the app to check ~/haproxy-1.4/conf/gear-registry.db will not find the new added gear info.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.create scalable app
2.embed mongodb/mysql to it
3.scale-up the app via REST API
4.check the /haproxy-status/ page via browser
5.check the ~/haproxy-1.4/conf/gear-registry.db file via ssh
4.the new added gear info will not show in /haproxy-status/ page
5.the new added gear info will not show in gear-registry.db
they should be
the new added gear info will show in the two places for scalable app without cartridge embedded.
this issue cannot be reproduced on devenv_1806
you can find the gear directory has been created under /var/lib/stickshift
This is not a bug -- the newly added gear for mysql will not show up in haproxy as that gear is not serving the application code. That new gear only has the data tier.
This needs a test case expected results update.
haproxy config + gear registry for haproxy [rsync really to push newly deployed code] should only have the serving gears in it.
Found out why the scaled up gear does not show up -- its because of the embed of mongo and mysql -- the env variables are messed up and sourcing those in fails.
This bug is really a duplicate of the underlying issue in bugz 826464.
*** This bug has been marked as a duplicate of bug 826464 ***