-
Bug
-
Resolution: Done
-
Normal
-
rhos-18.0.2
-
None
-
2
-
False
-
-
False
-
?
-
No Docs Impact
-
?
-
?
-
None
-
-
Bug Fix
-
Done
-
-
-
Critical
iscsi-starter.service must be disabled in EDPM node for iscsid container.
iscsi-starter.service is installed in EDPM node's image.
Its unit file is:
$ cat usr/lib/systemd/system/iscsi-starter.service [Unit] DefaultDependencies=no Before=sysinit.target iscsi.service RequiresMountsFor=/var/lib/iscsi/nodes ConditionDirectoryNotEmpty=/var/lib/iscsi/nodes [Service] Type=oneshot RemainAfterExit=true ExecStart=/usr/bin/systemctl start --no-block --job-mode=fail iscsi.service [Install] WantedBy=sysinit.target
And this unit is enabled. Due to that iscsi.service is started even though we disable iscsi.service in edpm-ansible.
We have to disable iscsi-starter.service as mandatory like we do for iscsi.service.
- name: Stop iscsi-starter.service ansible.builtin.systemd: name: iscsi-starter.service state: stopped enabled: false when: - ansible_facts.services["iscsi-starter.service"] is defined - ansible_facts.services["iscsi-starter.service"]["status"] != "not-found" - ansible_facts.services["iscsi-starter.service"]["status"] == "enabled"
The issue happens after the first reboot folloing the configuration by edpm-ansible.
This issue will happen all environments which uses iscsid container.