Red Hat Bugzilla – Bug 1025249
Should remove the gear-registry.db.lock for haproxy cartridge after migration
Last modified: 2015-05-14 19:32:12 EDT
Description of problem:
Create scalable app on stage ami, do server upgrade and gear migrate, check the haproxy cartridge dir in the scalable app. The gear-registry.db has been moved to gear home dir, but the lock file is still there.
Version-Release number of selected component (if applicable):
devenv-stage_528 to devenv_3973
Steps to Reproduce:
1.Create scalable apps on devenv-stage_528
2.Upgrade the server to devenv_3973
3.Restart broker, mcollective, clean broker cache and pending ops
4.Migrate the datastore
rhc-admin-migrate-datastore --version 2.0.35 --compatible
5.Migrate the gears
oo-admin-upgrade upgrade-node --version 2.0.35 --ignore-cartridge-version
6.Check the haproxy cartridge dir for scalable apps
The gear-registry.db.lock is still there.
The lock file should be removed since the gear-registry.db has been moved.
[jbeap2s-bmengmdev.dev.rhcloud.com conf]\> ls
gear-registry.db.lock haproxy.cfg haproxy.cfg.lock
After talking to Dan McPherson, we decided to close this as not a bug. It would have been nice to remove the lock file during this upgrade, but given the timing, it's a change we aren't comfortable doing right now. Apps created previously will continue to have this file, but it's harmless.
Do you think it is better to close this as WON'T FIX instead? Since you also thought it is "nice to remove but harmless"
Yes, that makes more sense - thanks!