openstack/tripleo-heat-templates
Code Issues Proposed changes

Disable iscsi.service to avoid iscsid on host from getting started

Browse Source 
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: I6c36cd15edfa53c3c76be9095ff40cecf451490d
Closes-Bug: #1833019
(cherry picked from commit 0d67ecaf75d9375e2a88479514ce6cb7e910ec5e)
This commit is contained in:
Takashi Kajinami 2019-06-17 09:56:07 +09:00
parent b8ebdfda4e
commit 5e70fa8691
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
deployment/iscsid/iscsid-container-puppet.yaml
View File

@ -111,6 +111,13 @@ outputs:
- name: Stop and disable iscsid.socket service
service: name=iscsid.socket state=stopped enabled=no
when: stat_iscsid_socket.stat.exists
- name: Check if iscsi.service is enabled
command: systemctl is-enabled --quiet iscsi.service
ignore_errors: True
register: iscsi_service_enabled_result
- name: Stop iscsi.service
service: name=iscsi.service state=stopped enabled=no
when: iscsi_service_enabled_result.rc == 0
upgrade_tasks: []
post_upgrade_tasks:
- when: step|int == 1