search

osism / issues

This repository is used for bug reports that are cross-project or not bound to a specific repository (or to an unknown repository).
https://www.osism.tech
1 stars 1 forks source link

Duplicate InitiatorNames after deployment iscsid Container #513

Closed zachelnet closed 1 year ago

zachelnet commented 1 year ago

When a deployment the iscsid container, they are the same initiator names every time:

ssh host1 docker exec -ti iscsid cat /etc/iscsi/initiatorname.iscsi
## DO NOT EDIT OR REMOVE THIS FILE!
## If you remove this file, the iSCSI daemon will not start.
## If you change the InitiatorName, existing access control lists
## may reject this initiator.  The InitiatorName must be unique
## for each iSCSI initiator.  Do NOT duplicate iSCSI InitiatorNames.
InitiatorName=iqn.1993-08.org.debian:01:1b3a3e559de

ssh host2 docker exec iscsid cat /etc/iscsi/initiatorname.iscsi
## DO NOT EDIT OR REMOVE THIS FILE!
## If you remove this file, the iSCSI daemon will not start.
## If you change the InitiatorName, existing access control lists
## may reject this initiator.  The InitiatorName must be unique
## for each iSCSI initiator.  Do NOT duplicate iSCSI InitiatorNames.
InitiatorName=iqn.1993-08.org.debian:01:1b3a3e559de

Image Version: 75f4ef47dc5f quay.io/osism/iscsid:2.0.874.20230501

zachelnet commented 1 year ago

Issue is coming by upgrade from xena to yoga

berendt commented 1 year ago

Please keep in mind that the use of LVM2/iSCSI is not recommended for productive use.