RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1533090 - fix displaying fencing levels
Summary: fix displaying fencing levels
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pcs
Version: 8.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 8.6
Assignee: Miroslav Lisik
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-10 12:59 UTC by Tomas Jelinek
Modified: 2022-05-10 15:24 UTC (History)
10 users (show)

Fixed In Version: pcs-0.10.11-1.el8
Doc Type: Bug Fix
Doc Text:
Cause: Configured regular expressions are indistinguishable from node names when displaying fencing levels. Consequence: User cannot tell difference between node names and regular expressions when displaying fencing levels. Fix: Output of the `pcs stonith level [config]` command informs if a target is a regexp. Result: Regular expressions and node names are distinguishable when displaying fencing levels.
Clone Of:
Environment:
Last Closed: 2022-05-10 14:50:42 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1261116 0 medium CLOSED Allow targeting by attribute in fencing topology 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker CLUSTERQE-5140 0 None None None 2021-10-25 19:44:58 UTC
Red Hat Issue Tracker CLUSTERQE-5494 0 None None None 2022-03-15 09:01:16 UTC
Red Hat Product Errata RHEA-2022:1978 0 None None None 2022-05-10 14:51:15 UTC

Internal Links: 1261116

Description Tomas Jelinek 2018-01-10 12:59:53 UTC 
Description of problem:
Support for specifying targets in fencing levels by regular expressions has been implemented in bz1261116. The problem is that regular expressions are indistinguishable from node names when displaying fencing levels.


Version-Release number of selected component (if applicable):
pcs-0.9.162-2.el7


How reproducible:
always, easily


Steps to Reproduce:
# pcs stonith show
 xvmNode1       (stonith:fence_xvm):    Started rh74-node1
 xvmNode2       (stonith:fence_xvm):    Started rh74-node2
 xvmNode3       (stonith:fence_xvm):    Started rh74-node1
# pcs stonith level add 1 rh74-node1 xvmNode1
# pcs stonith level add 2 "regexp%rh74-node" xvmNode2
# pcs stonith show
 xvmNode1       (stonith:fence_xvm):    Started rh74-node1
 xvmNode2       (stonith:fence_xvm):    Started rh74-node2
 xvmNode3       (stonith:fence_xvm):    Started rh74-node1
 Target: rh74-node1
   Level 1 - xvmNode1
 Target: rh74-node
   Level 2 - xvmNode2


Actual results:
The second target looks like it applies to rh74-node node but in fact it is a regular expression.


Expected results:
Target: regular expression: rh74-node
or similar
Comment 3 RHEL Program Management 2021-02-15 07:34:30 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 9 RHEL Program Management 2021-09-04 07:26:58 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 11 Miroslav Lisik 2021-10-07 12:36:17 UTC 
Created attachment 1830364 [details]
proposed fix + tests

Updated command:
  * pcs stonith level [config]

Test:
  * configure a stonith level with regex target with command `pcs stonith level add`
  * run `pcs stonith level`, output informs that target is a regexp.
Comment 13 Miroslav Lisik 2021-11-02 09:18:25 UTC 
DevTestResults:

[root@r8-node-01 ~]# rpm -q pcs
pcs-0.10.11-1.el8.x86_64

[root@r8-node-01 ~]# pcs stonith
  * fence-scsi  (stonith:fence_scsi):    Started r8-node-01
  * fence-r8-node-01    (stonith:fence_xvm):     Started r8-node-01
  * fence-r8-node-02    (stonith:fence_xvm):     Started r8-node-02
  * fence-r8-node-03    (stonith:fence_xvm):     Started r8-node-03

[root@r8-node-01 ~]# pcs stonith level add 1 r8-node-01 fence-r8-node-01
[root@r8-node-01 ~]# pcs stonith level add 1 r8-node-02 fence-r8-node-02
[root@r8-node-01 ~]# pcs stonith level add 1 r8-node-03 fence-r8-node-03
[root@r8-node-01 ~]# pcs stonith level add 2 regexp%r8-node fence-scsi

[root@r8-node-01 ~]# pcs stonith level
Target: r8-node-01
  Level 1 - fence-r8-node-01
Target: r8-node-02
  Level 1 - fence-r8-node-02
Target: r8-node-03
  Level 1 - fence-r8-node-03
Target (regexp): r8-node
  Level 2 - fence-scsi
Comment 18 svalasti 2022-02-24 14:53:53 UTC 
## BEFORE
[root@virt-043 ~]# rpm -q pcs
pcs-0.10.10-4.el8.x86_64
[root@virt-043 ~]# pcs stonith status
  * fence-virt-043	(stonith:fence_xvm):	 Started virt-043
  * fence-virt-044	(stonith:fence_xvm):	 Started virt-044
  * fence-virt-045	(stonith:fence_xvm):	 Started virt-045

[root@virt-043 ~]# pcs stonith level add 1 virt-043 fence-virt-043

[root@virt-043 ~]# pcs stonith level add 2 regexp%virt-04[4-5] fence-virt-044 fence-virt-045

[root@virt-043 ~]# pcs stonith status
  * fence-virt-043	(stonith:fence_xvm):	 Started virt-043
  * fence-virt-044	(stonith:fence_xvm):	 Started virt-044
  * fence-virt-045	(stonith:fence_xvm):	 Started virt-045
 Target: virt-043
   Level 1 - fence-virt-043
 Target: virt-04[4-5]
   Level 2 - fence-virt-044,fence-virt-045

[root@virt-043 ~]# pcs stonith level add 3 regexp%virt-0[3-5]{2} fence-virt-043 fence-virt-044 fence-virt-045

[root@virt-043 ~]# pcs stonith status
  * fence-virt-043	(stonith:fence_xvm):	 Started virt-043
  * fence-virt-044	(stonith:fence_xvm):	 Started virt-044
  * fence-virt-045	(stonith:fence_xvm):	 Started virt-045
 Target: virt-043
   Level 1 - fence-virt-043
 Target: virt-04[4-5]
   Level 2 - fence-virt-044,fence-virt-045
 Target: virt-0[3-5]{2}
   Level 3 - fence-virt-043,fence-virt-044,fence-virt-045

[root@virt-043 ~]# pcs stonith level verify

[root@virt-043 ~]# echo $?
0
> Output does not showing information about usage of reg. expressions.

## 2. Adding fencing level specifying almost the same target (with and without regular expression)
[root@virt-043 ~]# pcs stonith status
  * fence-virt-043	(stonith:fence_xvm):	 Started virt-043
  * fence-virt-044	(stonith:fence_xvm):	 Started virt-044
  * fence-virt-045	(stonith:fence_xvm):	 Started virt-045

[root@virt-043 ~]# pcs stonith level add 1 virt-044 fence-virt-044

[root@virt-043 ~]# pcs stonith level add 1 regexp%virt-044 fence-virt-044

[root@virt-043 ~]# pcs stonith status
  * fence-virt-043	(stonith:fence_xvm):	 Started virt-043
  * fence-virt-044	(stonith:fence_xvm):	 Started virt-044
  * fence-virt-045	(stonith:fence_xvm):	 Started virt-045
 Target: virt-044
   Level 1 - fence-virt-044
 Target: virt-044
   Level 1 - fence-virt-044

[root@virt-043 ~]# pcs stonith level verify

[root@virt-043 ~]# echo $?
0
> Output showing no difference between the fencing level specified by the regular expr. and string.


## AFTER
[root@virt-043 ~]# rpm -q pcs
pcs-0.10.12-6.el8.x86_64
[root@virt-043 ~]# pcs stonith status
  * fence-virt-043	(stonith:fence_xvm):	 Started virt-043
  * fence-virt-044	(stonith:fence_xvm):	 Started virt-044
  * fence-virt-045	(stonith:fence_xvm):	 Started virt-045

[root@virt-043 ~]# pcs stonith level add 1 virt-043 fence-virt-043

[root@virt-043 ~]# pcs stonith level add 2 regexp%virt-04[4-5] fence-virt-044 fence-virt-045

[root@virt-043 ~]# pcs stonith status
  * fence-virt-043	(stonith:fence_xvm):	 Started virt-043
  * fence-virt-044	(stonith:fence_xvm):	 Started virt-044
  * fence-virt-045	(stonith:fence_xvm):	 Started virt-045
 Target: virt-043
   Level 1 - fence-virt-043
 Target (regexp): virt-04[4-5]
   Level 2 - fence-virt-044,fence-virt-045

[root@virt-043 ~]# pcs stonith level add 3 regexp%virt-0[3-5]{2} fence-virt-043 fence-virt-044 fence-virt-045

[root@virt-043 ~]# pcs stonith status
  * fence-virt-043	(stonith:fence_xvm):	 Started virt-043
  * fence-virt-044	(stonith:fence_xvm):	 Started virt-044
  * fence-virt-045	(stonith:fence_xvm):	 Started virt-045
 Target: virt-043
   Level 1 - fence-virt-043
 Target (regexp): virt-04[4-5]
   Level 2 - fence-virt-044,fence-virt-045
 Target (regexp): virt-0[3-5]{2}
   Level 3 - fence-virt-043,fence-virt-044,fence-virt-045

[root@virt-043 ~]# pcs stonith level verify

[root@virt-043 ~]# echo $?
0

# Removing fencing level
[root@virt-043 ~]# pcs stonith level remove 3 target regexp%virt-0[3-5]{2}

[root@virt-043 ~]# pcs stonith level remove 2 target regexp%virt-04[4-5]

[root@virt-043 ~]# pcs stonith level remove 1 target virt-043

[root@virt-043 ~]# pcs stonith status
  * fence-virt-043	(stonith:fence_xvm):	 Started virt-043
  * fence-virt-044	(stonith:fence_xvm):	 Started virt-044
  * fence-virt-045	(stonith:fence_xvm):	 Started virt-045
> OK.
## 2. Adding fencing level specifying almost the same target (with and without regular expression)
 [root@virt-043 ~]# pcs stonith status
  * fence-virt-043	(stonith:fence_xvm):	 Started virt-043
  * fence-virt-044	(stonith:fence_xvm):	 Started virt-044
  * fence-virt-045	(stonith:fence_xvm):	 Started virt-045

[root@virt-043 ~]# pcs stonith level add 1 virt-044 fence-virt-044

[root@virt-043 ~]# pcs stonith level add 1 regexp%virt-044 fence-virt-044

[root@virt-043 ~]# pcs stonith status
  * fence-virt-043	(stonith:fence_xvm):	 Started virt-043
  * fence-virt-044	(stonith:fence_xvm):	 Started virt-044
  * fence-virt-045	(stonith:fence_xvm):	 Started virt-045
 Target: virt-044
   Level 1 - fence-virt-044
 Target (regexp): virt-044
   Level 1 - fence-virt-044

> Fencing targets are now distinguishable.

[root@virt-043 ~]# pcs stonith level verify

[root@virt-043 ~]# echo $?
0
[root@virt-043 ~]# pcs stonith level remove 1 target virt-044

[root@virt-043 ~]# pcs stonith level remove 1 target regexp%virt-044

[root@virt-043 ~]# pcs stonith status
  * fence-virt-043	(stonith:fence_xvm):	 Started virt-043
  * fence-virt-044	(stonith:fence_xvm):	 Started virt-044
  * fence-virt-045	(stonith:fence_xvm):	 Started virt-045

> OK.
Comment 20 errata-xmlrpc 2022-05-10 14:50:42 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 (pcs bug fix and enhancement update), 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/RHEA-2022:1978
Note You need to log in before you can comment on or make changes to this bug.