To Reproduce Steps to reproduce the behavior:

1. Stop `iscsid` service
2. Starting tripleo_iscsid services fails 

Expected behavior

• ISCSI container and service should start smoothly 

Bug impact

• Customer is unable to perform any activity on the compute node w.r.t VMs as tripleo_iscsi is required for volume attachment and detachment operation 
• Also one VM is stuck in rebooting state due to incorrect volume states

Known workaround

• Manually Updating a containers with rpms of version 
  6.2.1.2-2.1.gita8fcb37.el8_4

iscsi-initiator-utils
iscsi-initiator-utils-iscsiuio