Disable iscsi.service to avoid iscsid on host from getting started
When some stale shutdown happens on the node, iscsi.service detects
remaining information about iscsi connection, and recovers connections
based on the information, with starting iscsid service on host.
This causes a collision between iscsid on host and iscsid in container,
which makes iscsid container keep restarting.
This patch makes sure that iscsi.service on host is disabled
when we deploy iscsid container, to avoid iscsid on host is started
unexpectedly.
Reviewed: https:/ /review. opendev. org/665564 /git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ commit/ ?id=0d67ecaf75d 9375e2a88479514 ce6cb7e910ec5e
Committed: https:/
Submitter: Zuul
Branch: master
commit 0d67ecaf75d9375 e2a88479514ce6c b7e910ec5e
Author: Takashi Kajinami <email address hidden>
Date: Mon Jun 17 09:56:07 2019 +0900
Disable iscsi.service to avoid iscsid on host from getting started
When some stale shutdown happens on the node, iscsi.service detects
remaining information about iscsi connection, and recovers connections
based on the information, with starting iscsid service on host.
This causes a collision between iscsid on host and iscsid in container,
which makes iscsid container keep restarting.
This patch makes sure that iscsi.service on host is disabled
when we deploy iscsid container, to avoid iscsid on host is started
unexpectedly.
Change-Id: I6c36cd15edfa53 c3c76be9095ff40 cecf451490d
Closes-Bug: #1833019