[Bug 1865523] Re: [bionic] fence_scsi not working properly with 1.1.18-2ubuntu1.1
SUMMARY: One using packages from: https://launchpad.net/~ubuntu-server-ha/+archive/ubuntu/staging in Ubuntu Bionic will be workedaround temporarily (until fixes are released) for the bugs: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1865523 https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1866119 ** Summary changed: - [bionic] fence_scsi not working properly with 1.1.18-2ubuntu1.1 + [bionic] fence_scsi not working properly with Pacemaker 1.1.18-2ubuntu1.1 -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1865523 Title: [bionic] fence_scsi not working properly with Pacemaker 1.1.18-2ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1865523/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1865523] Re: [bionic] fence_scsi not working properly with 1.1.18-2ubuntu1.1
A PPA can be currently found at : https://launchpad.net/~ubuntu-server- ha/+archive/ubuntu/staging I'm adjusting the SRU but, meanwhile, that PPA provides a working version for Ubuntu Bionic. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1865523 Title: [bionic] fence_scsi not working properly with 1.1.18-2ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1865523/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1865523] Re: [bionic] fence_scsi not working properly with 1.1.18-2ubuntu1.1
** No longer affects: pacemaker (Ubuntu) ** No longer affects: pacemaker (Ubuntu Bionic) ** Description changed: + OBS: I have split this bug into 2 bugs: + - fence-agents (this) and pacemaker (LP: #1866119) + SRU: fence-agents [Impact] * fence_scsi is not currently working in a share disk environment * all clusters relying in fence_scsi and/or fence_scsi + watchdog won't be able to start the fencing agents OR, in worst case scenarios, the fence_scsi agent might start but won't make scsi reservations in the shared scsi disk. [Test Case] * having a 3-node setup, nodes called "clubionic01, clubionic02, clubionic03", with a shared scsi disk (fully supporting persistent reservations) /dev/sda, one might try the following command: sudo fence_scsi --verbose -n clubionic01 -d /dev/sda -k 3abe -o off from nodes "clubionic02 or clubionic03" and check if the reservation worked: (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 * having a 3-node setup, nodes called "clubionic01, clubionic02, clubionic03", with a shared scsi disk (fully supporting persistent reservations) /dev/sda, with corosync and pacemaker operational and running, one might try: rafaeldtinoco@clubionic01:~$ crm configure crm(live)configure# property stonith-enabled=on crm(live)configure# property stonith-action=off crm(live)configure# property no-quorum-policy=stop crm(live)configure# property have-watchdog=true crm(live)configure# property symmetric-cluster=true crm(live)configure# commit crm(live)configure# end crm(live)# end rafaeldtinoco@clubionic01:~$ crm configure primitive fence_clubionic \ stonith:fence_scsi params \ pcmk_host_list="clubionic01 clubionic02 clubionic03" \ devices="/dev/sda" \ meta provides=unfencing And see that crm_mon won't show fence_clubionic resource operational. [Regression Potential] - * Comments #3 and #4 show this new version fully working. - - * This fix has a potential of breaking other "nowadays working" fencing agent. If that happens, I suggest that ones affected revert previous to previous package AND open a bug against either pacemaker and/or fence-agents. + * Comments #3 and #4 show this new version fully working. + + * This fix has a potential of breaking other "nowadays working" fencing + agent. If that happens, I suggest that ones affected revert previous to + previous package AND open a bug against either pacemaker and/or fence- + agents. * Judging by this issue, it is very likely that any Ubuntu user that have tried using fence_scsi has probably migrated to a newer version because fence_scsi agent is broken since its release. * The way I fixed fence_scsi was this: I packaged pacemaker in latest 1.1.X version and kept it "vanilla" so I could bisect fence-agents. At that moment I realized that bisecting was going to be hard because there were multiple issues, not only one. I backported the latest fence-agents together with Pacemaker 1.1.19-0 and saw that it worked. From then on, I bisected the following intervals: 4.3.0 .. 4.4.0 (eoan - working) 4.2.0 .. 4.3.0 4.1.0 .. 4.2.0 4.0.25 .. 4.1.0 (bionic - not working) In each of those intervals I discovered issues. For example, Using 4.3.0 I faced problems so I had to backport fixes that were in between 4.4.0 and 4.3.0. Then, backporting 4.2.0, I faced issues so I had to backport fixes from the 4.3.0 <-> 4.2.0 interval. I did this until I was at 4.0.25 version, current Bionic fence-agents version. [Other Info] * Original 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" \
[Bug 1865523] Re: [bionic] fence_scsi not working properly with 1.1.18-2ubuntu1.1
** Description changed: + SRU: fence-agents + + [Impact] + + * fence_scsi is not currently working in a share disk environment + + * all clusters relying in fence_scsi and/or fence_scsi + watchdog won't + be able to start the fencing agents OR, in worst case scenarios, the + fence_scsi agent might start but won't make scsi reservations in the + shared scsi disk. + + [Test Case] + + * having a 3-node setup, nodes called "clubionic01, clubionic02, + clubionic03", with a shared scsi disk (fully supporting persistent + reservations) /dev/sda, one might try the following command: + + sudo fence_scsi --verbose -n clubionic01 -d /dev/sda -k 3abe -o off + + from nodes "clubionic02 or clubionic03" and check if the reservation + worked: + + (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 + + * having a 3-node setup, nodes called "clubionic01, clubionic02, + clubionic03", with a shared scsi disk (fully supporting persistent + reservations) /dev/sda, with corosync and pacemaker operational and + running, one might try: + + rafaeldtinoco@clubionic01:~$ crm configure + crm(live)configure# property stonith-enabled=on + crm(live)configure# property stonith-action=off + crm(live)configure# property no-quorum-policy=stop + crm(live)configure# property have-watchdog=true + crm(live)configure# property symmetric-cluster=true + crm(live)configure# commit + crm(live)configure# end + crm(live)# end + + rafaeldtinoco@clubionic01:~$ crm configure primitive fence_clubionic \ + stonith:fence_scsi params \ + pcmk_host_list="clubionic01 clubionic02 clubionic03" \ + devices="/dev/sda" \ + meta provides=unfencing + + And see that crm_mon won't show fence_clubionic resource operational. + + [Regression Potential] + + * Judging by this issue, it is very likely that any Ubuntu user that + have tried using fence_scsi has probably migrated to a newer version + because fence_scsi agent is broken since its release. + + * The way I fixed fence_scsi was this: + + I packaged pacemaker in latest 1.1.X version and kept it "vanilla" so I + could bisect fence-agents. At that moment I realized that bisecting was + going to be hard because there were multiple issues, not only one. I + backported the latest fence-agents together with Pacemaker 1.1.19-0 and + saw that it worked. + + From then on, I bisected the following intervals: + + 4.3.0 .. 4.4.0 (eoan - working) + 4.2.0 .. 4.3.0 + 4.1.0 .. 4.2.0 + 4.0.25 .. 4.1.0 (bionic - not working) + + In each of those intervals I discovered issues. For example, Using 4.3.0 + I faced problems so I had to backport fixes that were in between 4.4.0 + and 4.3.0. Then, backporting 4.2.0, I faced issues so I had to backport + fixes from the 4.3.0 <-> 4.2.0 interval. I did this until I was at + 4.0.25 version, current Bionic fence-agents version. + + [Other Info] + + * Original 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 + 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 + 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
[Bug 1865523] Re: [bionic] fence_scsi not working properly with 1.1.18-2ubuntu1.1
# Demonstration of fence_scsi fencing a node: (k)rafaeldtinoco@clubionic03:~/.../upstream$ cat /etc/network/interfaces auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp # iscsi auto eth1 iface eth1 inet static address 10.250.1.12/24 # private auto eth2 iface eth2 inet static address 10.250.3.12/24 # public auto eth3 iface eth3 inet static address 10.250.98.12/24 (k)rafaeldtinoco@clubionic03:~/.../upstream$ sudo iptables -A INPUT -i eth2 -j DROP (k)rafaeldtinoco@clubionic01:~$ crm_mon -1 Stack: corosync Current DC: clubionic01.private (version 1.1.19-1.1.19) - partition with quorum Last updated: Tue Mar 3 21:24:55 2020 Last change: Tue Mar 3 20:25:56 2020 by root via cibadmin on clubionic01.private 3 nodes configured 1 resource configured Online: [ clubionic01.private clubionic02.private ] OFFLINE: [ clubionic03.private ] Active resources: fence_clubionic(stonith:fence_scsi): Started clubionic01.private (k)rafaeldtinoco@clubionic03:~/.../upstream$ sudo sg_persist --in --read-keys --device=/dev/sda LIO-ORG cluster.bionic. 4.0 Peripheral device type: disk PR generation=0x4, 2 registered reservation keys follow: 0x3abe 0x3abe0001 (k)rafaeldtinoco@clubionic03:~/.../upstream$ sudo dd if=/dev/zero of=/dev/sda bs=1M count=1 [ 3301.867294] print_req_error: critical nexus error, dev sda, sector 0 [ 3301.868543] Buffer I/O error on dev sda, logical block 0, lost async page write [ 3301.869956] Buffer I/O error on dev sda, logical block 1, lost async page write [ 3301.871430] Buffer I/O error on dev sda, logical block 2, lost async page write [ 3301.872929] Buffer I/O error on dev sda, logical block 3, lost async page write [ 3301.874448] Buffer I/O error on dev sda, logical block 4, lost async page write [ 3301.875963] Buffer I/O error on dev sda, logical block 5, lost async page write [ 3301.877486] Buffer I/O error on dev sda, logical block 6, lost async page write [ 3301.879000] Buffer I/O error on dev sda, logical block 7, lost async page write [ 3301.880481] Buffer I/O error on dev sda, logical block 8, lost async page write [ 3301.882014] Buffer I/O error on dev sda, logical block 9, lost async page write 1+0 records in 1+0 records out 1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.0227557 s, 46.1 MB/s -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1865523 Title: [bionic] fence_scsi not working properly with 1.1.18-2ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1865523/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1865523] Re: [bionic] fence_scsi not working properly with 1.1.18-2ubuntu1.1
Now I'm going to work with this package and check needed Pacemaker fixes. After that I'm going to propose both merges together. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1865523 Title: [bionic] fence_scsi not working properly with 1.1.18-2ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1865523/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1865523] Re: [bionic] fence_scsi not working properly with 1.1.18-2ubuntu1.1
# 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 Date: Mon Jul 24 14:12:15 2017 fence_scsi: add FIPS support commit eae9d029b7073e7eb8c7ba4df9ec19b755a8f603 Author: Oyvind Albrigtsen Date: Wed Sep 27 12:26:38 2017 fix for ignored options commit c6f29a653114523e9ac3644aed958b4bb43f3b41 Author: Oyvind Albrigtsen Date: Wed Sep 27 12:42:39 2017 Maintain ABI compatibility for external agents commit 746fd55b061aa28b27aac5a1bb38714a95812592 Author: Reid Wahl Date: Fri Apr 6 18:31:30 2018 Low: fence_scsi: Remove period from cmd string commit bec154345d2291c9051c16277de9054387dc9707 Author: Oyvind Albrigtsen 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 Date: Wed May 23 12:51:23 2018 fence_scsi: fix python3 encoding error #206 commit f77297b654586bf539e78957f26cae1d22c6f081 Author: Oyvind Albrigtsen 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 -0009. commit 1c4a64ca803831b44c96c75022abe5bb8713cd1a Author: Oyvind Albrigtsen 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 Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1865523 Title: [bionic] fence_scsi not working properly with 1.1.18-2ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1865523/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1865523] Re: [bionic] fence_scsi not working properly with 1.1.18-2ubuntu1.1
# Demonstration of fence_scsi agent working in Bionic: (k)rafaeldtinoco@clubionic01:~/.../upstream$ sudo dpkg -i ./*.deb dpkg: warning: downgrading fence-agents from 4.4.0-2 to 4.0.25-2ubuntu1 (Reading database ... 85434 files and directories currently installed.) Preparing to unpack .../fence-agents_4.0.25-2ubuntu1_amd64.deb ... Unpacking fence-agents (4.0.25-2ubuntu1) over (4.4.0-2) ... Preparing to unpack .../fence-agents_4.4.0-2_amd64.deb ... Unpacking fence-agents (4.4.0-2) over (4.0.25-2ubuntu1) ... Setting up fence-agents (4.4.0-2) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... (k)rafaeldtinoco@clubionic01:~/.../upstream$ 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@clubionic01:~/.../upstream$ systemctl restart pacemaker (k)rafaeldtinoco@clubionic02:~/.../upstream$ crm_mon -1 Stack: corosync Current DC: clubionic03.private (version 1.1.19-1.1.19) - partition with quorum Last updated: Tue Mar 3 21:16:04 2020 Last change: Tue Mar 3 20:25:56 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@clubionic01:~/.../upstream$ sudo sg_persist --in --read-keys --device=/dev/sda LIO-ORG cluster.bionic. 4.0 Peripheral device type: disk PR generation=0x3, 3 registered reservation keys follow: 0x3abe 0x3abe0001 0x3abe0002 (k)rafaeldtinoco@clubionic01:~/.../upstream$ sudo sg_persist -r /dev/sda LIO-ORG cluster.bionic. 4.0 Peripheral device type: disk PR generation=0x3, Reservation follows: Key=0x3abe0001 scope: LU_SCOPE, type: Write Exclusive, registrants only -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1865523 Title: [bionic] fence_scsi not working properly with 1.1.18-2ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1865523/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1865523] Re: [bionic] fence_scsi not working properly with 1.1.18-2ubuntu1.1
To make this work I had to use pacemaker from upstream (Vanilla) version:
1.1.19-0
$ dpkg -l | grep 1.1.19 | awk '{print $2" "$3}'
libcib4:amd64 1.1.19-0ubuntu1
libcrmcluster4:amd64 1.1.19-0ubuntu1
libcrmcommon3:amd64 1.1.19-0ubuntu1
libcrmservice3:amd64 1.1.19-0ubuntu1
liblrmd1:amd64 1.1.19-0ubuntu1
libpe-rules2:amd64 1.1.19-0ubuntu1
libpe-status10:amd64 1.1.19-0ubuntu1
libpengine10:amd64 1.1.19-0ubuntu1
libstonithd2:amd64 1.1.19-0ubuntu1
libtransitioner2:amd64 1.1.19-0ubuntu1
pacemaker 1.1.19-0ubuntu1
pacemaker-cli-utils 1.1.19-0ubuntu1
pacemaker-common 1.1.19-0ubuntu1
pacemaker-doc 1.1.19-0ubuntu1
pacemaker-resource-agents 1.1.19-0ubuntu1
AND fence-agents from Ubuntu Eoan:
fence-agents 4.2.1-1
Only after that "combination" I was able to make fence_scsi agent to
work:
(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="clubionic01.private clubionic02.private
clubionic03.private" devices="/dev/sda" \
meta provides=unfencing
property cib-bootstrap-options: \
have-watchdog=false \
dc-version=1.1.19-1.1.19 \
cluster-infrastructure=corosync \
cluster-name=clubionic \
stonith-enabled=true \
stonith-action=off \
no-quorum-policy=stop
with proper reservations being made:
(k)rafaeldtinoco@clubionic03:~$ sudo sg_persist --in --read-keys
--device=/dev/sda
LIO-ORG cluster.bionic. 4.0
Peripheral device type: disk
PR generation=0x4, 3 registered reservation keys follow:
0x3abe0002
0x3abe
0x3abe0001
** Also affects: fence-agents (Ubuntu)
Importance: Undecided
Status: New
** Changed in: pacemaker (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: pacemaker (Ubuntu)
Importance: Medium => Undecided
** Changed in: pacemaker (Ubuntu)
Status: Confirmed => Triaged
** Also affects: pacemaker (Ubuntu Focal)
Importance: Undecided
Status: Triaged
** Also affects: fence-agents (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: pacemaker (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: fence-agents (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: pacemaker (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: fence-agents (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: pacemaker (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: fence-agents (Ubuntu Disco)
Importance: Undecided
Status: New
** No longer affects: pacemaker (Ubuntu Focal)
** No longer affects: pacemaker (Ubuntu Eoan)
** No longer affects: pacemaker (Ubuntu Disco)
** Changed in: pacemaker (Ubuntu)
Status: Triaged => Fix Released
** Changed in: pacemaker (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: pacemaker (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: pacemaker (Ubuntu Bionic)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
** Changed in: fence-agents (Ubuntu Eoan)
Status: New => Fix Released
** Changed in: fence-agents (Ubuntu Focal)
Status: New => Fix Released
** Changed in: fence-agents (Ubuntu Disco)
Status: New => Confirmed
** Changed in: fence-agents (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: fence-agents (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: fence-agents (Ubuntu Disco)
Importance: Undecided => Medium
** Changed in: pacemaker (Ubuntu Bionic)
Importance: High => Medium
** Changed in: fence-agents (Ubuntu Bionic)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
** Changed in: fence-agents (Ubuntu Disco)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1865523
Title:
[bionic] fence_scsi not working properly with 1.1.18-2ubuntu1.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1865523/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
