Bug 2142681

Summary:	"pcs node utilization" command sets incorrect attribute value
Product:	Red Hat Enterprise Linux 8	Reporter:	Ken Gaillot <kgaillot>
Component:	pacemaker	Assignee:	Chris Lumens <clumens>
Status:	CLOSED ERRATA	QA Contact:	cluster-qe <cluster-qe>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	8.7	CC:	cfeist, cluster-maint, msmazova
Target Milestone:	rc	Keywords:	Triaged, ZStream
Target Release:	8.8	Flags:	pm-rhel: mirror+
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	pacemaker-2.1.5-1.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2142683 2144870 (view as bug list)		Environment:
Last Closed:	2023-05-16 08:35:22 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:	2.1.5
Embargoed:
Bug Depends On:
Bug Blocks:	2142683, 2144870

Description Ken Gaillot 2022-11-14 21:11:48 UTC

Description of problem: The "pcs node utilization <node> <name>=<value>" command should set a permanent node attribute with the given name and value in a utilization block. In the 8.7 packages, it instead uses "utilization" as the value.


Version-Release number of selected component (if applicable): 8.7


How reproducible: reliably


Steps to Reproduce:
1. Configure and start a cluster.
2. Set a node utilization attribute with "pcs node utilization".
3. Check the attribute value with "pcs node utilization".

Actual results: The attribute value is "utilization".


Expected results: The attribute value is the one specified when set.

Comment 1 Ken Gaillot 2022-11-14 21:17:01 UTC

Fixed upstream by commit 566fb0c5

Comment 8 Chris Lumens 2022-12-07 15:39:55 UTC

Upon closer inspection, this bug is not a regression.  It was introduced in Pacemaker-2.1.5-rc1, not 2.1.3 as previously thought.  It was not in any RHEL release.  The commit message with the fix does reference the commit that introduced the bug correctly, and it has been fixed in a subsequent RC.  It's worth checking that it is fixed.  It's probably worth scrubbing the CCFR text and any references to a regression from this bug report.

Comment 9 Chris Lumens 2022-12-07 15:54:36 UTC

Note to QE:  The bug was introduced in -rc1 and fixed in -rc2.  There was not a -rc1 build for RHEL, so you should just need to confirm that the bug was never introduced.

Comment 10 Markéta Smazová 2022-12-19 12:30:29 UTC

[root@virt-507 ~]# rpm -q pacemaker
pacemaker-2.1.5-4.el8.x86_64

[root@virt-507 ~]# pcs status
Cluster name: STSRHTS29018
Status of pacemakerd: 'Pacemaker is running' (last updated 2022-12-19 13:28:23 +01:00)
Cluster Summary:
  * Stack: corosync
  * Current DC: virt-507 (version 2.1.5-4.el8-a3f44794f94) - partition with quorum
  * Last updated: Mon Dec 19 13:28:23 2022
  * Last change:  Mon Dec 19 13:24:06 2022 by root via cibadmin on virt-507
  * 2 nodes configured
  * 2 resource instances configured

Node List:
  * Online: [ virt-507 virt-508 ]

Full List of Resources:
  * fence-virt-507	(stonith:fence_xvm):	 Started virt-507
  * fence-virt-508	(stonith:fence_xvm):	 Started virt-508

Daemon Status:
  corosync: active/enabled
  pacemaker: active/enabled
  pcsd: active/enabled


[root@virt-507 ~]# pcs node utilization
Node Utilization:

[root@virt-507 ~]# pcs node utilization virt-507 test=1
[root@virt-507 ~]# pcs node utilization virt-508 test=1
 
[root@virt-507 ~]# pcs node utilization
Node Utilization:
 virt-507: test=1
 virt-508: test=1

[root@virt-507 ~]# pcs node utilization virt-507
Node Utilization:
 virt-507: test=1

[root@virt-507 ~]# pcs node utilization virt-508
Node Utilization:
 virt-508: test=1

Result: "pcs node utilization" works correctly

marking VERIFIED in pacemaker-2.1.5-4.el8

Comment 12 errata-xmlrpc 2023-05-16 08:35:22 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 (pacemaker 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/RHBA-2023:2818