Red Hat Bugzilla – Bug 1008424
[fork][origin_runtime_215] Existing gears do not migrate to new structure after server upgrade to fork_ami_deploy
Last modified: 2015-05-14 19:28:37 EDT
Description of problem:
Migrate devenv_stage_465 to fork_ami_deploy_833. The old apps will not be updated to new structure.
Version-Release number of selected component (if applicable):
from devenv_stage_465 to fork_ami_deploy_833
Steps to Reproduce:
1. Start an instance of devenv_stage_465
2. Create apps on this instance
3. Copy /root/devenv_local and /etc/yum.repo.d from the fork_ami_deploy_833 instance to devenv_stage_465 instance.
4. Do the following steps to finish the migrate:
a).yum clean all
b).yum -y update --enablerepo devenv-local
c).Restart the services: rhc-broker mcollective activemq
d).Clean broker cache
e)./usr/bin/rhc-admin-migrate-datastore --non-compatible --version 2.0.32 (NOTE: the script is using 2.0.32 instead of 2.0.33, so I use 32 here)
f).oo-admin-upgrade upgrade-node --version 2.0.33 --ignore-cartridge-version
The old apps are not migrated to new structures. If SSH to the app, the dependency folder is not there.
Apps should be migrate to use the new structure.
New created apps (created after migrate) will not be impacted. They will use new structure
Created attachment 798226 [details]
The attached log is from the instance of devenv_stage_465. I packaged /tmp/oo-upgrate.
We have a card for the upgrades: https://trello.com/c/dghNbF5U