Bug 1598969

Summary: ocf::heartbeat:iSCSILogicalUnit -> This NodeACL already exists in configFS
Product: Red Hat Enterprise Linux 7 Reporter: Strahil Nikolov <hunter86_bg>
Component: resource-agentsAssignee: Oyvind Albrigtsen <oalbrigt>
Status: CLOSED ERRATA QA Contact: cluster-qe <cluster-qe>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.5CC: agk, cfeist, cluster-maint, fdinitto, mjuricek, phagara
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: resource-agents-4.1.1-32.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1692413 (view as bug list) Environment:
Last Closed: 2020-03-31 19:47:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1692413    
Attachments:
Description Flags
debug start of iSCSILogicalUnit resource and cluster backup none

Description Strahil Nikolov 2018-07-07 12:08:29 UTC
Created attachment 1457154 [details]
debug start of iSCSILogicalUnit resource and cluster backup

Description of problem:
iSCSILogicalUnit fails to start the resource from the first time with the error 'This NodeACL already exists in configFS' once the resource has failed on all nodes and the resource got clear && cleanup - the resource starts successfully.

Version-Release number of selected component (if applicable):
corosync-2.4.3-2.el7_5.1.x86_64
corosynclib-2.4.3-2.el7_5.1.x86_64
pacemaker-1.1.18-11.el7_5.3.x86_64
pacemaker-cli-1.1.18-11.el7_5.3.x86_64
pacemaker-cluster-libs-1.1.18-11.el7_5.3.x86_64
pacemaker-libs-1.1.18-11.el7_5.3.x86_64
resource-agents-3.9.5-124.el7.x86_64
targetcli-2.1.fb46-6.el7_5.noarch


How reproducible:
Always

Steps to Reproduce:
1. Disable firewall or allow port 7000/tcp
2. Set selinux to permissive
3. Configure 3 nodes with drbd and test them prior to setting it up in the cluster configuration:
3.1. Create drbd0 config file:
# cat /etc/drbd.d/drbd0.res 
resource drbd0 {
protocol C;
net {
        cram-hmac-alg sha1;
        shared-secret "SomePass";
}

 
volume 0 {
	device /dev/drbd0;
	disk /dev/drbd/drbd0;
	meta-disk internal;
}
 
on drbd1 {
	address 192.168.122.48:7000;
	node-id 1;
}
on drbd2 {
	address 192.168.122.49:7000;
	node-id 2;
}
on drbd3 {
	address 192.168.122.50:7000;
	node-id 3;
}
 
connection-mesh {
  hosts drbd1 drbd2 drbd3;
}
 
}

3.2 Prepare local storage for drbd on all nodes: 
drbdadm create-md drbd0
drbdadm up drbd0
3.3 Make one node primary for initial sync:
drbdadm primary --force drbd0

4.Configure the cluster by using the "pcs config restore cluster.bkp.tar.bz2" -> provided in the attached zip file


Actual results:
iSCSILogicalUnit fails to start properly.Manual intervention is needed via:
'pcs resource clear iscsi-lun0 && pcs resource cleanup iscsi-lun0'.
Once the nodes get rebooted -> they need to fail starting the resource and cleaned up again.

Expected results:
iSCSILogictalUnit to work as expected

Additional info:
I'm attaching the cluster config backup and output of the debug-start generated via:
pcs resource disable iscsi-lun0
#export OCF_ROOT=/usr/lib/ocf
#export OCF_RESKEY_allowed_initiators='iqn.2018-01.com.example:client01'
#export OCF_RESKEY_lun=0
#export OCF_RESKEY_path=/dev/drbd0
#export OCF_RESKEY_target_iqn='iqn.2018-01.com.example:centos'
#bash -x /usr/lib/ocf/resource.d/heartbeat/iSCSILogicalUnit start

Comment 2 Strahil Nikolov 2018-09-04 19:37:03 UTC
Have you managed to reproduce the issue ?

Comment 3 Oyvind Albrigtsen 2019-02-20 09:40:41 UTC
It seems like this patch should solve this issue: https://github.com/ClusterLabs/resource-agents/pull/1239

Comment 5 Patrik Hagara 2019-03-26 09:30:24 UTC
qa_ack+, reproducer in comment#4

Comment 10 Oyvind Albrigtsen 2019-07-30 09:28:03 UTC
Additional patch for iSCSILogicalUnit: https://github.com/ClusterLabs/resource-agents/pull/1371

Comment 13 Strahil Nikolov 2020-03-10 22:40:26 UTC
Shouldn't we close this one with errata ?

Comment 16 errata-xmlrpc 2020-03-31 19:47:12 UTC
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-2020:1067