Blame SOURCES/bz2036633-01-Make-ocf-linbit-drbd-agent-pass-OCF-validation.patch

1dae0a
From 46b079a93d1817f9c1d6a7403c70b30f59d19c20 Mon Sep 17 00:00:00 2001
1dae0a
From: Tomas Jelinek <tojeline@redhat.com>
1dae0a
Date: Tue, 4 Jan 2022 12:56:56 +0100
1dae0a
Subject: [PATCH 2/5] Make ocf:linbit:drbd agent pass OCF validation
1dae0a
1dae0a
---
1dae0a
 data/ocf-1.0.rng | 18 ++++++++----------
1dae0a
 1 file changed, 8 insertions(+), 10 deletions(-)
1dae0a
1dae0a
diff --git a/data/ocf-1.0.rng b/data/ocf-1.0.rng
1dae0a
index 36ba4611..1e14a83b 100644
1dae0a
--- a/data/ocf-1.0.rng
1dae0a
+++ b/data/ocf-1.0.rng
1dae0a
@@ -169,16 +169,14 @@ RNGs. Thank you.
1dae0a
       <optional>
1dae0a
         <element name="content">
1dae0a
           <choice>
1dae0a
-            <attribute name="type">
1dae0a
-              <choice>
1dae0a
-                <value>boolean</value>
1dae0a
-                <value>string</value>
1dae0a
-                <value>integer</value>
1dae0a
-                <value>second</value>
1dae0a
-                <value>int</value>
1dae0a
-                <value>time</value>
1dae0a
-              </choice>
1dae0a
-            </attribute>
1dae0a
+            
1dae0a
+              OCF 1.0 allows values: boolean, integer, string. Agents, however,
1dae0a
+              quite often use other values: int (fence agents), numeric
1dae0a
+              (ocf:linbit:drbd), second (fence agents), time (pacemaker
1dae0a
+              metadata). Since pcs doesn't actually care about the type, we
1dae0a
+              allow any type to keep compatibility with existing agents.
1dae0a
+            -->
1dae0a
+            <attribute name="type" />
1dae0a
             <group>
1dae0a
               
1dae0a
                 used by fence agents and processed by pcs even though it is not
1dae0a
-- 
1dae0a
2.31.1
1dae0a