Bug 1939533

Summary:	pacemaker generates invalid xml for certain failures [rhel-8.3.0.z]
Product:	Red Hat Enterprise Linux 8	Reporter:	RHEL Program Management Team <pgm-rhel-tools>
Component:	pacemaker	Assignee:	Chris Lumens <clumens>
Status:	CLOSED ERRATA	QA Contact:	cluster-qe <cluster-qe>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	8.2	CC:	cfeist, clumens, cluster-maint, jwboyer, kgaillot, nwahl, pkomarov
Target Milestone:	rc	Keywords:	Regression, Triaged, ZStream
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	pacemaker-2.0.4-6.el8_3.2	Doc Type:	Bug Fix
Doc Text:	Cause: Pacemaker can record certain resource operation history entries with a fake call ID of -1, but the status schema restricts the field to a nonnegative integer. Consequence: When such history is present, configuration changes via pcs fail with a "does not conform to the schema" message. Fix: The schema now allows any integer. Result: These history entries do not prevent further configuration commands.	Story Points:	---
Clone Of:	1931332	Environment:
Last Closed:	2021-04-06 14:07:34 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:	1931332
Bug Blocks:

Comment 5 pkomarov 2021-03-21 11:34:31 UTC

Verified ,
[stack@undercloud-0 ~]$ ansible controller -b -mshell -a'rpm -qa|grep pacemaker-2'
[WARNING]: Found both group and host with same name: undercloud
[WARNING]: Consider using the yum, dnf or zypper module rather than running 'rpm'.  If you need to use command because yum, dnf or zypper is insufficient you can add 'warn: false' to this
command task or set 'command_warnings=False' in ansible.cfg to get rid of this message.
controller-0 | CHANGED | rc=0 >>
pacemaker-2.0.4-6.el8_3.2.x86_64
controller-1 | CHANGED | rc=0 >>
pacemaker-2.0.4-6.el8_3.2.x86_64
controller-2 | CHANGED | rc=0 >>
pacemaker-2.0.4-6.el8_3.2.x86_64


[root@controller-0 ~]# /usr/sbin/crm_mon --one-shot --as-xml --inactive 2>&1 | tee /tmp/crm
[root@controller-0 ~]# xmllint /tmp/crm --relaxng /usr/share/pacemaker/crm_mon.rng -
[full output here : http://pastebin.test.redhat.com/949151]
/tmp/crm validates

Comment 6 pkomarov 2021-03-21 11:48:42 UTC

Moving back to on_qa , sent too soon

Comment 7 pkomarov 2021-03-21 12:08:42 UTC

Verified ,
[stack@undercloud-0 ~]$ ansible controller -b -mshell -a'rpm -qa|grep pacemaker-2'
[WARNING]: Found both group and host with same name: undercloud
[WARNING]: Consider using the yum, dnf or zypper module rather than running 'rpm'.  If you need to use command because yum, dnf or zypper is insufficient you can add 'warn: false' to this
command task or set 'command_warnings=False' in ansible.cfg to get rid of this message.
controller-0 | CHANGED | rc=0 >>
pacemaker-2.0.4-6.el8_3.2.x86_64
controller-1 | CHANGED | rc=0 >>
pacemaker-2.0.4-6.el8_3.2.x86_64
controller-2 | CHANGED | rc=0 >>
pacemaker-2.0.4-6.el8_3.2.x86_64



[root@controller-0 ~]# /usr/sbin/crm_mon --one-shot --as-xml --inactive 2>&1 | tee /tmp/crm
[root@controller-0 ~]# xmllint /tmp/crm --relaxng /usr/share/pacemaker/crm_mon.rng -
[...]
[full output here : http://pastebin.test.redhat.com/949153]
/tmp/crm validates

Comment 12 errata-xmlrpc 2021-04-06 14:07:34 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-2021:1088