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>
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.
(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.
(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.