Project

General

Profile

Bug #8633

expected reports, component keys

Added by Janos Mattyasovszky over 1 year ago. Updated 10 months ago.

Status:
Released
Priority:
3
Category:
Documentation
Target version:
Target version (plugin):
Severity:
User visibility:
Effort required:
Priority:

Description

When you have a technique, and:
- the path it is located below is: /var/rudder/configuration-repository/techniques/Janos/MyMotdFile/1.0
- is <MULTIINSTANCE>false</MULTIINSTANCE>
- have <SECTION name="MOTD entry" multivalued="false">

Then apparently Rudder expects a Report, that has a Component name of the report is the directory your technique is inside:

Missing report

This was fixes as soon I made it component="true" in the metadata.xml for the <SECTION/>

Please document this behavior, or make it more clear that you need to have at least one section with component="true" that you have a report on your technique, it was not very clear from http://www.rudder-project.org/foswiki/Development/TechniqueXML

report_section_name.png - Missing report (13.4 KB) Janos Mattyasovszky, 2016-07-06 10:41

Associated revisions

Revision 772d71c0
Added by Nicolas CHARLES 11 months ago

Fixes #8633: expected reports, component keys

History

#1 Updated by François ARMAND over 1 year ago

  • Priority changed from N/A to 3
  • Target version set to 2.11.23

Thanks for reporting, the doc should even enforce the use of "component=true / component key", and we should even add a warning in the parser to help user understand that without them, they will be surprised. We can't change the format itself for compatibility reason before some guards.

#2 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 2.11.23 to 2.11.24

#3 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 2.11.24 to 308

#4 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 308 to 3.1.14

#5 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 3.1.14 to 3.1.15

#6 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 3.1.15 to 3.1.16

#7 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 3.1.16 to 3.1.17

#8 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 3.1.17 to 3.1.18

#9 Updated by Nicolas CHARLES 11 months ago

  • Status changed from New to Pending technical review
  • Assignee changed from Nicolas CHARLES to Alexis MOUSSET

Documentation has been updated here
http://www.rudder-project.org/foswiki/Development/TechniqueXML

Thank you for your remark Janos

#10 Updated by Alexis MOUSSET 11 months ago

This now lives in http://www.rudder-project.org/doc-4.0/_technique_reference.html, so the patch should be done on the rudder-doc repo. Redirection from foswiki to the manual is still not merged because some rely on the new FAQ.

#11 Updated by Alexis MOUSSET 11 months ago

  • Status changed from Pending technical review to New
  • Assignee changed from Alexis MOUSSET to Nicolas CHARLES

#12 Updated by Nicolas CHARLES 11 months ago

  • Status changed from New to In progress

#13 Updated by Nicolas CHARLES 11 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to Alexis MOUSSET
  • Pull Request set to https://github.com/Normation/rudder-doc/pull/277

#14 Updated by Nicolas CHARLES 11 months ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100

#15 Updated by Vincent MEMBRÉ 10 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.1.18, 3.2.11, 4.0.3 and 4.1.0~beta3 which were released today.

Also available in: Atom PDF