os_brick may require InitiatorName in /etc/iscsi/initiatorname.iscsi
before iscsid is invoked via iscsid.socket with iscsiadm. Cloud images
including MAAS ones have "GenerateName=yes" instead of "InitiatorName="
on purpose not to clone the initiator name. Let's initialize it so
Cinder units can be fully ready to accept iSCSI based subordinate and
storage backend charms.
Closes-Bug: 1825809
Change-Id: I413bbb29dd609e0c86ac3691556f37a9fcc13439
(cherry picked from commit bde329d973f2d66f800a15d0f4721fc949a609b1)
Reviewed: https:/ /review. opendev. org/c/openstack /charm- cinder/ +/819838 /opendev. org/openstack/ charm-cinder/ commit/ 82bc1e227b33b3b a7a548dab5e4bda b638f9529e
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/21.10
commit 82bc1e227b33b3b a7a548dab5e4bda b638f9529e
Author: Nobuto Murata <email address hidden>
Date: Wed Sep 22 13:53:33 2021 +0900
Make sure iscsid has a unique InitiatorName
os_brick may require InitiatorName in /etc/iscsi/ initiatorname. iscsi
before iscsid is invoked via iscsid.socket with iscsiadm. Cloud images
including MAAS ones have "GenerateName=yes" instead of "InitiatorName="
on purpose not to clone the initiator name. Let's initialize it so
Cinder units can be fully ready to accept iSCSI based subordinate and
storage backend charms.
Closes-Bug: 1825809 0c86ac3691556f3 7a9fcc13439 f800a15d0f4721f c949a609b1)
Change-Id: I413bbb29dd609e
(cherry picked from commit bde329d973f2d66