-
Bug
-
Resolution: Done-Errata
-
Undefined
-
None
-
None
-
fence-agents-4.2.1-127.el8
-
None
-
None
-
rhel-sst-high-availability
-
ssg_filesystems_storage_and_HA
-
13
-
17
-
8
-
QE ack, Dev ack
-
False
-
-
None
-
None
-
Pass
-
None
-
None
What were you trying to do that didn't work?
If an iSCSI client establishes a connection with a device using an ISID (say X) and registers/reserves with the device using a key, the key is associated with the I_T nexus (with ISID X). Now if a device reconnects for some reason (like client reboots), it establishes a new iSCSI connection (with ISID Y) and fence agent tries to register again. However fence_scsi looks up the reservation key for the device, sees that it matches with the key and skips sending a new registration command assuming that the key belongs to it (ignoring the ISID).
This can cause the iSCSI initiator to have no access to the device since it is not registered.
Patches:
https://github.com/ClusterLabs/fence-agents/pull/529
https://github.com/ClusterLabs/fence-agents/pull/558
Please provide the package NVR for which bug is seen:
fence-agents-4.10.0-55.el9
How reproducible:
100%
Steps to reproduce
- Follow instructions in https://github.com/ClusterLabs/fence-agents/pull/558#issuecomment-1721830437
Expected results
Doesnt fail
Actual results
Fails
- clones
-
RHEL-5396 fence_scsi: fix registration handling if ISID conflicts
- Closed
- links to
-
RHBA-2023:121041 fence-agents bug fix and enhancement update
- mentioned on