Project

General

Profile

Actions

Bug #22691

closed

Technique with empty description causes error in webapp log in Rudder 7.3

Added by Nicolas CHARLES 12 months ago. Updated 12 months ago.

Status:
Rejected
Priority:
N/A
Category:
Web - Config management
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
It bothers me each time
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
44
Name check:
To do
Fix check:
To do
Regression:
No

Description

The error message complains that description is mandatory but is missing (empty):

Consistancy: Description is mandatory but wasn't found for variable spec elt: <INPUT>
        <NAME>D0BD40C2-7270-4B49-BCE3-55F349DC3027</NAME>
        <DESCRIPTION/>
        <LONGDESCRIPTION/>
        <CONSTRAINT>
          <TYPE>textarea</TYPE>
          <MAYBEEMPTY>false</MAYBEEMPTY>
        </CONSTRAINT>
      </INPUT>

[2023-04-26 10:57:48+0200] ERROR techniques.reader - Error with technique at path: '/ncf_techniques/test/1.0/metadata.xml', it will be ignored. Error: Chained: Couldn't parse Section in test/1.0 -> test for XML: <SECTION name="Technique parameters">
      <INPUT>
        <NAME>D0BD40C2-7270-4B49-BCE3-55F349DC3027</NAME>
        <DESCRIPTION/>
        <LONGDESCRIPTION/>
        <CONSTRAINT>
          <TYPE>textarea</TYPE>
          <MAYBEEMPTY>false</MAYBEEMPTY>
        </CONSTRAINT>
      </INPUT>
    </SECTION>; cause was: Chained: In test/1.0 -> test, couldn't parse variable <INPUT>
        <NAME>D0BD40C2-7270-4B49-BCE3-55F349DC3027</NAME>
        <DESCRIPTION/>
        <LONGDESCRIPTION/>
        <CONSTRAINT>
          <TYPE>textarea</TYPE>
          <MAYBEEMPTY>false</MAYBEEMPTY>
        </CONSTRAINT>
      </INPUT>; cause was: Consistancy: Description is mandatory but wasn't found for variable spec elt: <INPUT>
        <NAME>D0BD40C2-7270-4B49-BCE3-55F349DC3027</NAME>
        <DESCRIPTION/>
        <LONGDESCRIPTION/>
        <CONSTRAINT>
          <TYPE>textarea</TYPE>
          <MAYBEEMPTY>false</MAYBEEMPTY>
        </CONSTRAINT>
      </INPUT>
[2023-04-26 10:57:48+0200] ERROR techniques.reader - Error with technique at path: '/ncf_techniques/test/1.0/metadata.xml', it will be ignored. Error: Chained: Couldn't parse Section in test/1.0 -> test for XML: <SECTION name="Technique parameters">
      <INPUT>
        <NAME>D0BD40C2-7270-4B49-BCE3-55F349DC3027</NAME>
        <DESCRIPTION/>
        <LONGDESCRIPTION/>
        <CONSTRAINT>
          <TYPE>textarea</TYPE>
          <MAYBEEMPTY>false</MAYBEEMPTY>
        </CONSTRAINT>
      </INPUT>
    </SECTION>; cause was: Chained: In test/1.0 -> test, couldn't parse variable <INPUT>
        <NAME>D0BD40C2-7270-4B49-BCE3-55F349DC3027</NAME>
        <DESCRIPTION/>
        <LONGDESCRIPTION/>
       <CONSTRAINT>
          <TYPE>textarea</TYPE>
          <MAYBEEMPTY>false</MAYBEEMPTY>
        </CONSTRAINT>
      </INPUT>; cause was: Consistancy: Description is mandatory but wasn't found for variable spec elt: <INPUT>
        <NAME>D0BD40C2-7270-4B49-BCE3-55F349DC3027</NAME>
        <DESCRIPTION/>
        <LONGDESCRIPTION/>
        <CONSTRAINT>
          <TYPE>textarea</TYPE>
          <MAYBEEMPTY>false</MAYBEEMPTY>
        </CONSTRAINT>
      </INPUT>
<pre> 

happens after an upgrade from 7.2

Technique content is
<pre>
{
  "id":"test",
  "version":"1.0",
  "category":"ncf_techniques",
  "description":"",
  "name":"test",
  "calls":[],
  "parameter":[
    {
      "id":"d0bd40c2-7270-4b49-bce3-55f349dc3027",
      "name":"",
      "description":"",
      "mayBeEmpty":false
    }
  ],
  "resources":[],
  "source":"editor" 
}
</pre>
happens after an upgrade
Actions

Also available in: Atom PDF