Project

General

Profile

Actions
Copy link

Bug #5031

closed

User story #4628: Only check a component status in the distributePolicy when it is present

logrotate.conf is generated in the wrong Technique directory

Added by Jonathan CLARKE almost 11 years ago. Updated almost 11 years ago.

Status:
Released
Priority:
2
Assignee:
Nicolas CHARLES
Category:
System techniques
Target version:
2.11.0~beta1
Pull Request:
https://github.com/Normation/rudder-t...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

From server-roles/metadata.xml:

     <TML name="rudder-logrotate">
       <OUTPATH>distributePolicy/logrotate.conf/rudder</OUTPATH>
       <INCLUDED>false</INCLUDED>
     </TML>

However, the CFEngine promises do indeed look for this file under server-roles:

      "/etc/logrotate.d/rudder" 
        edit_template => "${sys.workdir}/inputs/server-roles/logrotate.conf/rudder",
Actions
Copy link
 #1

Updated by Jonathan CLARKE almost 11 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Jonathan CLARKE to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/415
Actions
Copy link
 #2

Updated by Jonathan CLARKE almost 11 years ago

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

Applied in changeset policy-templates:commit:623d9ed9f45ed90487e7f565cdbb93dfbe4d3597.

Actions
Copy link
 #3

Updated by Vincent MEMBRÉ almost 11 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.11.0~beta1 that was released yesterday.

Actions
Copy link

Also available in: Atom PDF