upgrade-zulip-stage-2: Remove explicit process_fts_updates start.

Thanks to changes in restart-server, this is now already happening there.

(The restart-server changes were required to ensure that if the
upgrade failes and one just does
/home/zulip/deployments/next/restart-server to recover, the right
thing happens; so this is the correct resolution to the conflict).
This commit is contained in:
Tim Abbott
2018-08-03 15:20:03 -07:00
parent 69dcf3bac1
commit b8b97c98fb

View File

@@ -153,10 +153,6 @@ subprocess.check_call(["./manage.py", "create_realm_internal_bots"], preexec_fn=
logging.info("Restarting Zulip...") logging.info("Restarting Zulip...")
subprocess.check_output(["./scripts/restart-server"], preexec_fn=su_to_zulip) subprocess.check_output(["./scripts/restart-server"], preexec_fn=su_to_zulip)
if os.path.exists("/etc/supervisor/conf.d/zulip_db.conf"):
subprocess.check_call(["supervisorctl", "start", "process-fts-updates"], preexec_fn=su_to_zulip)
logging.info("Upgrade complete!") logging.info("Upgrade complete!")
subprocess.check_call(["./scripts/purge-old-deployments"]) subprocess.check_call(["./scripts/purge-old-deployments"])