Update post-backup-unlock.sh.erb (#289)

* Update post-backup-unlock.sh.erb If the timeout fails then the workers never get started, but monit will eventually restart the web process if the CF install eventually recovers, leaving a VM that is half working (with an unhealthy bosh state) after the script runs. We could also change the exit behavior of the time out with `set +x` (or is it e? I forget), but it would seem that the only point of timing out is to alert the operator to a possible issue since the CC API can still restart. * Update post-backup-unlock.sh.erb Putting the sleep back in after reviewing this [conversation](#132). It seems to be have been added to allow time for route propagation --------- Co-authored-by: MerricdeLauney <[email protected]>
cloudfoundry · Mar 15, 2023 · 4a72175 · 4a72175
1 parent e00d2d7
commit 4a72175
Showing 1 changed file with 2 additions and 3 deletions.
diff --git a/jobs/cloud_controller_ng/templates/post-backup-unlock.sh.erb b/jobs/cloud_controller_ng/templates/post-backup-unlock.sh.erb
@@ -14,10 +14,9 @@ source /var/vcap/packages/capi_utils/syslog_utils.sh
   fi
 
   monit_start_job cloud_controller_ng
-  wait_for_server_to_become_healthy <%= "localhost:#{p("cc.external_port")}/healthz" %> <%= p("cc.post_bbr_healthcheck_timeout_in_seconds") %>
-  sleep 30
-
   <% (1..(p("cc.jobs.local.number_of_workers"))).each do |index| %>
   monit_start_job cloud_controller_worker_local_<%= index %>
   <% end %>
+  wait_for_server_to_become_healthy <%= "localhost:#{p("cc.external_port")}/healthz" %> <%= p("cc.post_bbr_healthcheck_timeout_in_seconds") %>
+  sleep 30
 <% end %>