Description of problem: After recovering from a iscsi path down, windows 2016 will retry a STPG even though success is returned. In the logs we will see this repeated: Jul 17 01:28:41 commando tcmu-runner: 2018-07-17 01:28:41.768 60588 [ERROR] tcmu_emulate_set_tgt_port_grps:750 rbd/poolA.win2k16_vol3: Failing STPG for group 2 Jul 17 01:28:41 commando tcmu-runner: tcmu_emulate_set_tgt_port_grps:750 rbd/poolA.win2k16_vol3: Failing STPG for group 2 Jul 17 01:28:42 commando tcmu-runner: 2018-07-17 01:28:42.017 60588 [WARN] tcmu_block_device:395 rbd/poolA.win2k16_vol3: Kernel does not support the block_dev action. Jul 17 01:28:42 commando tcmu-runner: tcmu_block_device:395 rbd/poolA.win2k16_vol3: Kernel does not support the block_dev action. Jul 17 01:28:42 commando tcmu-runner: 2018-07-17 01:28:42.018 60588 [WARN] tcmu_rbd_lock:735 rbd/poolA.win2k16_vol3: Acquired exclusive lock. The block_dev/unblock warnings can be ignored. The problem is that the first STPG fails for a currently unknown reason. It is retried as expected. This works, but then the initiator sends the STPG again. The above sequence then repeats about 46 times. The initiator then tries the second path and it works the first time and the initiator does not retry. block_device:395 rbd/poolA.win2k16_vol3: Kernel does not support the block_dev action. Jul 17 01:28:43 catalina tcmu-runner: tcmu_block_device:395 rbd/poolA.win2k16_vol3: Kernel does not support the block_dev action. Jul 17 01:28:43 catalina tcmu-runner: 2018-07-17 01:28:43.222 59934 [WARN] tcmu_rbd_lock:735 rbd/poolA.win2k16_vol3: Acquired exclusive lock. Jul 17 01:28:43 catalina tcmu-runner: tcmu_rbd_lock:735 rbd/poolA.win2k16_vol3: Acquired exclusive lock. Jul 17 01:28:43 catalina tcmu-runner: 2018-07-17 01:28:43.270 59934 [WARN] tcmu_unblock_device:418 rbd/poolA.win2k16_vol3: Kernel does not support the block_dev action. Jul 17 01:28:43 catalina tcmu-runner: tcmu_unblock_device:418 rbd/poolA.win2k16_vol3: Kernel does not support the block_dev action. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:2819