# For Ubuntu Bionic:
Okay, after bisecting fence-scsi and monitoring all its functions I was
able to isolate the patches that I need to take to bionic to make it
compatible with existing version and, at the same time, operational:
Note: all tests were conducted with Pacemaker v1.1.19-0ubuntu1 and this
is not the default in Ubuntu Bionic. I have maintained "vanilla"
Pacemaker v1.1.19 in order to better isolate all fixes for fence-agents.
Now I'm able to create a fixed fence-agent package for Ubuntu Bionic AND
fix Pacemaker.
# Ubuntu Bionic SRU: Fence Agents v4.0.25 PLUS the following
fixes/commits ordered by date:
commit 81b8370844f5aecaee5e7178d82670c70399d824
Author: Oyvind Albrigtsen <oalbr...@redhat.com>
Date: Mon Jul 24 14:12:15 2017
fence_scsi: add FIPS support
commit eae9d029b7073e7eb8c7ba4df9ec19b755a8f603
Author: Oyvind Albrigtsen <oalbr...@redhat.com>
Date: Wed Sep 27 12:26:38 2017
fix for ignored options
commit c6f29a653114523e9ac3644aed958b4bb43f3b41
Author: Oyvind Albrigtsen <oalbr...@redhat.com>
Date: Wed Sep 27 12:42:39 2017
Maintain ABI compatibility for external agents
commit 746fd55b061aa28b27aac5a1bb38714a95812592
Author: Reid Wahl <nrw...@protonmail.com>
Date: Fri Apr 6 18:31:30 2018
Low: fence_scsi: Remove period from cmd string
commit bec154345d2291c9051c16277de9054387dc9707
Author: Oyvind Albrigtsen <oalbr...@redhat.com>
Date: Thu Apr 19 11:30:53 2018
fence_scsi: fix plug-parameter and keep support for nodename to
avoid regressions
commit 335aca4e54e4ec46b9b5d86ef30a7d9348e6a216
Author: Valentin Vidic <valentin.vi...@carnet.hr>
Date: Wed May 23 12:51:23 2018
fence_scsi: fix python3 encoding error #206
commit f77297b654586bf539e78957f26cae1d22c6f081
Author: Oyvind Albrigtsen <oalbr...@redhat.com>
Date: Fri Nov 2 08:24:56 2018
fence_scsi: fix incorrect SCSI key when node ID is 10 or higher
The last four digits of the SCSI key will be zero padded digit
between 0000-0009.
commit 1c4a64ca803831b44c96c75022abe5bb8713cd1a
Author: Oyvind Albrigtsen <oalbr...@redhat.com>
Date: Wed May 22 08:13:34 2019
fence_scsi: detect node ID using new format, and fallback to old format
before failing
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1865523
Title:
[bionic] fence_scsi not working properly with 1.1.18-2ubuntu1.1
Status in fence-agents package in Ubuntu:
Fix Released
Status in pacemaker package in Ubuntu:
Fix Released
Status in fence-agents source package in Bionic:
Confirmed
Status in pacemaker source package in Bionic:
Confirmed
Status in fence-agents source package in Disco:
Confirmed
Status in fence-agents source package in Eoan:
Fix Released
Status in fence-agents source package in Focal:
Fix Released
Bug description:
Trying to setup a cluster with an iscsi shared disk, using fence_scsi
as the fencing mechanism, I realized that fence_scsi is not working in
Ubuntu Bionic. I first thought it was related to Azure environment
(LP: #1864419), where I was trying this environment, but then, trying
locally, I figured out that somehow pacemaker 1.1.18 is not fencing
the shared scsi disk properly.
Note: I was able to "backport" vanilla 1.1.19 from upstream and
fence_scsi worked. I have then tried 1.1.18 without all quilt patches
and it didnt work as well. I think that bisecting 1.1.18 <-> 1.1.19
might tell us which commit has fixed the behaviour needed by the
fence_scsi agent.
(k)rafaeldtinoco@clubionic01:~$ crm conf show
node 1: clubionic01.private
node 2: clubionic02.private
node 3: clubionic03.private
primitive fence_clubionic stonith:fence_scsi \
params pcmk_host_list="10.250.3.10 10.250.3.11 10.250.3.12"
devices="/dev/sda" \
meta provides=unfencing
property cib-bootstrap-options: \
have-watchdog=false \
dc-version=1.1.18-2b07d5c5a9 \
cluster-infrastructure=corosync \
cluster-name=clubionic \
stonith-enabled=on \
stonith-action=off \
no-quorum-policy=stop \
symmetric-cluster=true
----
(k)rafaeldtinoco@clubionic02:~$ sudo crm_mon -1
Stack: corosync
Current DC: clubionic01.private (version 1.1.18-2b07d5c5a9) - partition with
quorum
Last updated: Mon Mar 2 15:55:30 2020
Last change: Mon Mar 2 15:45:33 2020 by root via cibadmin on
clubionic01.private
3 nodes configured
1 resource configured
Online: [ clubionic01.private clubionic02.private clubionic03.private
]
Active resources:
fence_clubionic (stonith:fence_scsi): Started
clubionic01.private
----
(k)rafaeldtinoco@clubionic02:~$ sudo sg_persist --in --read-keys
--device=/dev/sda
LIO-ORG cluster.bionic. 4.0
Peripheral device type: disk
PR generation=0x0, there are NO registered reservation keys
(k)rafaeldtinoco@clubionic02:~$ sudo sg_persist -r /dev/sda
LIO-ORG cluster.bionic. 4.0
Peripheral device type: disk
PR generation=0x0, there is NO reservation held
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1865523/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-ha
Post to : ubuntu-ha@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-ha
More help : https://help.launchpad.net/ListHelp
