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 2049722 - Resource ocf:pacemaker:attribute does not comply with the OCF 1.1 standard
Summary: Resource ocf:pacemaker:attribute does not comply with the OCF 1.1 standard
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pacemaker
Version: 8.6
Hardware: All
OS: All
Target Milestone: rc
: 8.7
Assignee: Chris Lumens
QA Contact: cluster-qe@redhat.com
Depends On:
TreeView+ depends on / blocked
Reported: 2022-02-02 15:35 UTC by Markéta Smazová
Modified: 2023-07-25 17:46 UTC (History)
4 users (show)

Fixed In Version: pacemaker-2.1.3-1.el8
Doc Type: No Doc Update
Doc Text:
This is mostly invisible to end users
Clone Of: 2049720
Last Closed: 2022-11-08 09:42:25 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker KCSOPP-1851 0 None None None 2023-07-25 17:46:37 UTC
Red Hat Issue Tracker RHELPLAN-110778 0 None None None 2022-02-02 15:48:55 UTC
Red Hat Product Errata RHBA-2022:7573 0 None None None 2022-11-08 09:42:42 UTC

Description Markéta Smazová 2022-02-02 15:35:46 UTC
+++ This bug was initially created as a clone of Bug #2049720 +++

Description of problem:
Resource ocf:pacemaker:attribute does not comply with the OCF 1.1 standard

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

How reproducible:
always, easily

Steps to Reproduce:
# curl -s https://raw.githubusercontent.com/ClusterLabs/OCF-spec/main/ra/1.1/ra-api.rng -o ocf1.1.rng

# crm_resource --show-metadata=ocf:pacemaker:attribute | xmllint --noout --relaxng ocf1.1.rng -
-:5: element longdesc: Relax-NG validity error : Did not expect element longdesc there
-:5: element longdesc: Relax-NG validity error : Element resource-agent has extra content: longdesc
- fails to validate

Actual results:
Resource metadata fails to validate with the rng scheme of the ocf 1.1 standard.

Expected results:
Resource metadata validate with the rng scheme of the ocf 1.1 standard.

Comment 1 Ken Gaillot 2022-02-14 19:45:34 UTC
Fixed upstream as of commit c078566a

Comment 6 Markéta Smazová 2022-06-07 17:08:37 UTC
after fix

[root@virt-535 ~]# rpm -q pacemaker pacemaker-cli

[root@virt-535 ~]# curl -s https://raw.githubusercontent.com/ClusterLabs/OCF-spec/main/ra/1.1/ra-api.rng -o ocf1.1.rng

[root@virt-535 ~]# crm_resource --show-metadata=ocf:pacemaker:attribute | xmllint --noout --relaxng ocf1.1.rng -
- validates

verified as SanityOnly in pacemaker-2.1.3-2.el8

Comment 8 errata-xmlrpc 2022-11-08 09:42:25 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.


Note You need to log in before you can comment on or make changes to this bug.