Project

General

Profile

Actions

User story #4628

closed

Only check a component status in the distributePolicy when it is present

Added by Matthieu CERDA over 8 years ago. Updated about 8 years ago.

Status:
Released
Priority:
2
Assignee:
Matthieu CERDA
Category:
System techniques
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:

Description

Only check a component status in the distributePolicy when it is present


Subtasks 4 (0 open4 closed)

User story #4629: Only check a component status in the distributePolicy when it is present (development)ReleasedJonathan CLARKE2014-03-15Actions
User story #4620: Let rudder-agent handle the logrotate files instead of packagesReleasedJonathan CLARKE2014-03-14Actions
Bug #5031: logrotate.conf is generated in the wrong Technique directoryReleasedNicolas CHARLES2014-06-15Actions
User story #5035: Adapt initial promises to only check components when presentReleasedNicolas CHARLES2014-06-15Actions

Related issues 1 (0 open1 closed)

Related to Rudder - User story #4621: Use templates in logrotate files to reduce the amount of themRejectedMatthieu CERDA2014-03-14Actions
Actions #1

Updated by Jonathan CLARKE over 8 years ago

  • Target version changed from 135 to 2.11.0~beta1
Actions #2

Updated by Jonathan CLARKE about 8 years ago

  • Status changed from 13 to 12
Actions #3

Updated by Jonathan CLARKE about 8 years ago

  • Project changed from 24 to Rudder
  • Category deleted (Techniques)
Actions #4

Updated by Jonathan CLARKE about 8 years ago

  • Category set to System techniques
  • Status changed from 12 to Pending release
Actions #5

Updated by Vincent MEMBRÉ about 8 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

Also available in: Atom PDF