Commit 73690d48 authored by Alejandro Rodríguez's avatar Alejandro Rodríguez

Inverse unicorn and redis steps in failback

Restarting unicorn may resolve an issue about redis expecting to be a master but being a slave, so we should do that first
parent 8b87ce8a
Pipeline #88975 passed with stage
in 17 seconds
......@@ -119,11 +119,11 @@ outside world
1. [ ] ↩️ {+ Fail-back Handler +}: Reconfigure every changed gstg node
1. bundle exec knife ssh roles:gstg-base "sudo chef-client"
1. [ ] ↩️ {+ Fail-back Handler +}: Clear cache on gstg web nodes to correct broadcast message cache
* `sudo gitlab-rake cache:clear:redis`
1. [ ] ↩️ {+ Fail-back Handler +}: Restart Unicorn and Sidekiq
* `bundle exec knife ssh 'roles:gstg-base AND omnibus-gitlab_gitlab_rb_unicorn_enable:true' 'sudo gitlab-ctl restart unicorn'`
* `bundle exec knife ssh 'roles:gstg-base AND omnibus-gitlab_gitlab_rb_sidekiq-cluster_enable:true' 'sudo gitlab-ctl restart sidekiq-cluster'`
1. [ ] ↩️ {+ Fail-back Handler +}: Clear cache on gstg web nodes to correct broadcast message cache
* `sudo gitlab-rake cache:clear:redis`
1. [ ] ↩️ {+ Fail-back Handler +}: Verify database replication is working
1. Create an issue on the Azure site and wait to see if it replicates successfully to the GCP site
1. [ ] ↩️ {+ Fail-back Handler +}: Verify https://gstg.gitlab.com reports it is a secondary in the blue banner on top
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment