Hide Forgot
Description of problem: upgrade devenv_stage_478 to fork_ami_208_864, after migration, show below error: (you can get detail info in attachment ) {"login":"openshift+migration2","app_name":"perl1s","gear_uuid":"4b0d8b56269211e3842412313b0ef580","version":"2.0.34","errors":["Upgrade failed with an unhandled exception: Cannot validate input secret_token: value should be a string Version-Release number of selected component (if applicable): upgrade devenv_stage_478 to fork_ami_208_864 How reproducible: Always Steps to Reproduce: 1. launch a devenv_stage_478 instance and create some apps 2. scp -r ~/devenv-local and /etc/yum.repos.d/* (from fork instance to same location on devenv-stage instance ) 3. yum -y update --enablerepo devenv-local 4. oo-admin-broker-cache --clear --console 5. Restart mcollective services and rhc-broker #service ruby193-mcollective restart #service rhc-broker restart 6. sh migrate_port_proxy all 7. oo-admin-clear-pending-ops --time 0 8. rhc-admin-migrate-datastore --non-compatible --version 2.0.34 9. oo-admin-upgrade upgrade-node --version 2.0.34 --ignore-cartridge-versio Actual results: after step9, show "Cannot validate input secret_token" error after migration in /tmp/oo-upgrade/upgrade_errors_ip-10-100-246-142 detail log has attached. Expected results: should migrate successfully without any error Additional info: do same migration test from devenv_478 to latest devenv (devenv_3832), migrate successfully without any error.
Created attachment 803359 [details] upgrade error log
This is the issue: 8. rhc-admin-migrate-datastore --non-compatible --version 2.0.34 show be 8. rhc-admin-migrate-datastore --compatible --version 2.0.34 For the secret tokens to be generated.
Confirmed it should be caused by missing the compatible migration as Jhon said, since it has both compatible and incompatible mongo migration this sprint. Upgraded and migrated from devenv-stage_478 to fork_ami_card_208_868, migration works correctly.