Re: CF rollback issue from v210 to v202


Lingesh Mouleeshwaran
 

Hi James,

Thanks a lot , Please could you tell us what is the clean way of doing
rollback from v210 to v202.

Regards
Lingesh M

On Mon, Jun 29, 2015 at 5:58 PM, James Bayer <jbayer(a)pivotal.io> wrote:

when you upgrade to a newer version of cf-release, it performs database
migrations. the message is likely telling you that cf-release v202 code in
the cloud controller is not compatible with the db migrations that were
performed when upgrading to cf-release v210.

On Mon, Jun 29, 2015 at 2:53 PM, Lingesh Mouleeshwaran <
lingeshmouleeshwaran(a)gmail.com> wrote:

Hello Team ,

we are able to upgrade cf 202 to v210 in development environment , incase
of any unknown issue we may want to rollback to 202. So we are trying to
rollback from 210 to 202. But bosh not able to complete the rollback
successfully. we are getting below error from bosh.

Error :

Started updating job api_z1
Started updating job api_z1 > api_z1/0 (canary). Failed: `api_z1/0' is
not running after update (00:14:53)

Error 400007: `api_z1/0' is not running after update


even we are able to ssh on api_z1 successfully. but found below issue in
cloud_controller_ng .

monit summary
The Monit daemon 5.2.4 uptime: 13m

Process 'cloud_controller_ng' Execution failed
Process 'cloud_controller_worker_local_1' not monitored
Process 'cloud_controller_worker_local_2' not monitored
Process 'nginx_cc' not monitored
Process 'metron_agent' running
Process 'check_mk' running
System 'system_6e1e4d43-f677-4dc6-ab8a-5b6152504918' running

logs from : /var/vcap/sys/log/cloud_controller_ng_ctl.err.log

[2015-06-29 21:18:55+0000] Tasks: TOP => db:migrate
[2015-06-29 21:18:55+0000] (See full trace by running task with --trace)
[2015-06-29 21:19:39+0000] ------------ STARTING cloud_controller_ng_ctl
at Mon Jun 29 21:19:36 UTC 2015 --------------
[2015-06-29 21:19:39+0000] rake aborted!
[2015-06-29 21:19:39+0000] Sequel::Migrator::Error: Applied migration
files not in file system:
20150306233007_increase_size_of_delayed_job_handler.rb,
20150311204445_add_desired_state_to_v3_apps.rb,
20150313233039_create_apps_v3_routes.rb,
20150316184259_create_service_key_table.rb,
20150318185941_add_encrypted_environment_variables_to_apps_v3.rb,
20150319150641_add_encrypted_environment_variables_to_v3_droplets.rb,
20150323170053_change_service_instance_description_to_text.rb,
20150323234355_recreate_apps_v3_routes.rb,
20150324232809_add_fk_v3_apps_packages_droplets_processes.rb,
20150325224808_add_v3_attrs_to_app_usage_events.rb,
20150327080540_add_cached_docker_image_to_droplets.rb,
20150403175058_add_index_to_droplets_droplet_hash.rb,
20150403190653_add_procfile_to_droplets.rb,
20150407213536_add_index_to_stack_id.rb,
20150421190248_add_allow_ssh_to_app.rb, 20150422000255_route_path_field.rb,
20150430214950_add_allow_ssh_to_spaces.rb,
20150501181106_rename_apps_allow_ssh_to_enable_ssh.rb,
20150514190458_fix_mysql_collations.rb,
20150515230939_add_case_insensitive_to_route_path.rb
cloud_controller_ng_ctl.err.log




Please any idea is some thing problem with rollback scripts during
rollback ??.

Regards
Lingesh M

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev


--
Thank you,

James Bayer

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.