Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 2096909

Summary:	Systemd and service resources do not comply with the OCF1.1 standard
Product:	Red Hat Enterprise Linux 9	Reporter:	Markéta Smazová <msmazova>
Component:	pacemaker	Assignee:	Ken Gaillot <kgaillot>
Status:	CLOSED MIGRATED	QA Contact:	cluster-qe <cluster-qe>
Severity:	low	Docs Contact:
Priority:	low
Version:	9.0	CC:	cluster-maint, tojeline
Target Milestone:	rc	Keywords:	MigratedToJIRA, Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	This is mostly invisible to end users	Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-22 19:39:32 UTC	Type:	Enhancement
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Markéta Smazová 2022-06-14 14:23:52 UTC

Description of problem:
	Unable to validate metadata for systemd and service resources with the ocf 1.1 standard schema.

Version-Release number of selected component (if applicable):
	pacemaker-2.1.2-4.el9.x86_64

How reproducible:
	always

Steps to Reproduce:
	1. curl -s https://raw.githubusercontent.com/ClusterLabs/OCF-spec/main/ra/1.1/ra-api.rng -o ocf1.1.rng
	2. crm_resource --show-metadata=service:sssd | xmllint --noout --relaxng ocf1.1.rng -

Actual results:
	-:9: element parameters: Relax-NG validity error : Expecting an element , got nothing
	- fails to validate

Expected results:
	Systemd and service resources metadata validate with the schema

Additional info:

It seems that the schema requires at least one element in "parameters":

	cat ocf1.1.rng | grep parameters
		<element name="parameters"> <oneOrMore>


But there are no elements in "parameters" for this service resource:

	crm_resource --show-metadata=service:sssd | grep parameters -C1
	  <shortdesc lang="en">systemd unit file for sssd</shortdesc>
	  <parameters/>
	  <actions>

Comment 1 Ken Gaillot 2022-06-14 15:04:11 UTC

Right, only OCF agents can validate against the OCF schema.

Pacemaker simulates OCF-like meta-data for non-OCF resources, but it can't be perfect since they don't actually support the OCF standard. At best we could supply an alternate schema for non-OCF meta-data.

Comment 2 Tomas Jelinek 2022-06-15 15:39:09 UTC

(In reply to Ken Gaillot from comment #1)
> Right, only OCF agents can validate against the OCF schema.

Interesting. I always thought, that pacemaker generates OCF valid meta-data for all non-OCF agents, so that the agents can be worked with as if they were truly OCF. What you said would suggest that this is not the case, and non-OCF agents and their meta-data potentially need to be handled differently.

Comment 3 Ken Gaillot 2022-06-15 17:28:59 UTC

(In reply to Tomas Jelinek from comment #2)
> (In reply to Ken Gaillot from comment #1)
> > Right, only OCF agents can validate against the OCF schema.
> 
> Interesting. I always thought, that pacemaker generates OCF valid meta-data
> for all non-OCF agents, so that the agents can be worked with as if they
> were truly OCF. What you said would suggest that this is not the case, and
> non-OCF agents and their meta-data potentially need to be handled
> differently.

Correct -- non-OCF agents don't support parameters for example, but the OCF standard requires at least one parameter to be specified. Technically they may not support all the required actions either, but Pacemaker probably already simulates those.

If we relax the requirement for parameters in the next OCF standard, I suppose we could make them compliant, which would be convenient.

Comment 5 RHEL Program Management 2023-09-22 19:37:52 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 6 RHEL Program Management 2023-09-22 19:39:32 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.