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.
Conflicts: docker/services/iscsid.yaml
Change-Id: I6c36cd15edfa53c3c76be9095ff40cecf451490d
Closes-Bug: #1833019
(cherry picked from commit 0d67ecaf75d9375e2a88479514ce6cb7e910ec5e)
(cherry picked from commit 5e70fa86918e7274e8ea02e79fa7a32e2ac22741)
Reviewed: https:/ /review. opendev. org/665825 /git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ commit/ ?id=0ff24b93973 378605219650b25 5ba2fda4730fba
Committed: https:/
Submitter: Zuul
Branch: stable/rocky
commit 0ff24b939733786 05219650b255ba2 fda4730fba
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.
Conflicts:
docker/ services/ iscsid. yaml
Change-Id: I6c36cd15edfa53 c3c76be9095ff40 cecf451490d e2a88479514ce6c b7e910ec5e) 4e8ea02e79fa7a3 2e2ac22741)
Closes-Bug: #1833019
(cherry picked from commit 0d67ecaf75d9375
(cherry picked from commit 5e70fa86918e727