ClusterLabs / ClusterLabs/resource-agents

iSCSITarget always fails to start (LIO-T mode)

Open
#1,026 10 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Shell
Stars
519
Forks
608
Avg merge
6d 1h
Merged PRs (30d)
7

Description

The iSCSITarget RA never succeeds in automatically starting a target. It seems to first create the target and then tries to create it again (which obviously fails), and then exit with error 1. Checking targetcli shows the target, so it's not exiting gracefully either.

Manually starting it twice with pcs resource debug-start does make it work, but then it still fails in a different way: it never adds the target portal so no connections from initiators can be made.

The target primitive is about as simple as it gets:

```
primitive iscsi0-target iSCSITarget \
params implementation=lio-t iqn="iqn.2017-08.access.net:prod-1-ha" \
op monitor interval=30s \
meta target-role=Started
```

corosync: 2.4.2
pacemaker: 1.1.16
targetcli-fb: 2.1.43
OS: Debian 9.1

The RA scripts were one revision behind the ones in this repo, the only difference was targetcli lock file sharing between LUN and Target setup. I replaced the ones I had with the ones from the repo, but that didn't change anything (and I didn't really expect it to).

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the iSCSITarget resource-agent scripts and reproduce the primitive with pcs resource debug-start while inspecting targetcli. Verify the automatic start does not create the target twice and that it adds the target portal so initiators can connect.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.