iscsi.service on host should be disabled to avoid iscsid is started at host when some stale shutdown happens
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Takashi Kajinami |
Bug Description
Since Queens, we run iscsid running inside container, and disable the one running on host.
However, when some stale shutdown happens, iscsi.service is started when booting that stale node,
and it launches iscsid.service on host.
This makes iscsid container stuck in "Restarting" with the following error.
~~~
Jun 14 17:11:12 compute-1 journal: INFO:__
Jun 14 17:11:12 compute-1 journal: INFO:__
Jun 14 17:11:12 compute-1 journal: INFO:__main__:Kolla config strategy set to: COPY_ALWAYS
Jun 14 17:11:12 compute-1 journal: INFO:__
Jun 14 17:11:12 compute-1 journal: INFO:__
Jun 14 17:11:12 compute-1 journal: INFO:__
Jun 14 17:11:12 compute-1 journal: INFO:__
Jun 14 17:11:12 compute-1 journal: INFO:__
Jun 14 17:11:12 compute-1 journal: INFO:__
Jun 14 17:11:12 compute-1 journal: ++ cat /run_command
Jun 14 17:11:12 compute-1 journal: Running command: '/usr/sbin/iscsid -f'
Jun 14 17:11:12 compute-1 journal: + CMD='/usr/
Jun 14 17:11:12 compute-1 journal: + ARGS=
Jun 14 17:11:12 compute-1 journal: + [[ ! -n '' ]]
Jun 14 17:11:12 compute-1 journal: + . kolla_extend_start
Jun 14 17:11:12 compute-1 journal: ++ [[ ! -f /etc/iscsi/
Jun 14 17:11:12 compute-1 journal: + echo 'Running command: '\''/usr/
Jun 14 17:11:12 compute-1 journal: + exec /usr/sbin/iscsid -f
Jun 14 17:11:12 compute-1 journal: iscsid: Can not bind IPC socket
~~~
Changed in tripleo: | |
importance: | Undecided → High |
tags: | added: idempotency queens-backport-potential rocky-backport-potential stein-backport-potential |
Changed in tripleo: | |
milestone: | none → train-2 |
Fix proposed to branch: master /review. opendev. org/665564
Review: https:/