From 72395ad46f41581a0bbac6d5b4194b3c0b4c109c Mon Sep 17 00:00:00 2001
From: Vladyslav Drok <vdrok@mirantis.com>
Date: Wed, 16 Aug 2017 11:36:08 +0300
Subject: [PATCH] Remove ensure_logs_exist check during upgrade

We now run services under systemd, and this check is not necessary in
this case. Follow-up to commit ee538d1e7c1a92cb8412713e03cdfbcdacad7fab
to grenade.

Change-Id: I84ca621f0200838c04e267101848dc7ca16a5cfe
---
 devstack/upgrade/upgrade.sh | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/devstack/upgrade/upgrade.sh b/devstack/upgrade/upgrade.sh
index 156f3e5703..e8105df152 100755
--- a/devstack/upgrade/upgrade.sh
+++ b/devstack/upgrade/upgrade.sh
@@ -77,8 +77,6 @@ iniset $IRONIC_CONF_FILE DEFAULT pin_release_version ${BASE_DEVSTACK_BRANCH#*/}
 
 ensure_started='ironic-conductor nova-compute '
 ensure_stopped=''
-# Don't succeed unless the services come up
-logs_exist="ir-cond"
 # Multinode grenade is designed to upgrade services only on primary node. And there is no way to manipulate
 # subnode during grenade phases. With this after upgrade we can have upgraded (new) services on primary
 # node and not upgraded (old) services on subnode.
@@ -113,7 +111,6 @@ if [[ -n "$ensure_stopped" ]]; then
 fi
 
 ensure_services_started $ensure_started
-ensure_logs_exist $logs_exist
 
 # We need these steps only in case of flat-network
 # NOTE(vsaienko) starting from Ocata when Neutron is restarted there is no guarantee that