Project

General

Profile

Actions

Bug #4479

closed

An unnecessary promise generation is launched right after making a new archive of the configuration

Added by François ARMAND almost 9 years ago. Updated almost 9 years ago.

Status:
Released
Priority:
3
Category:
Performance and scalability
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Regression:

Description

Whenever an archive of configuration is done, a promise generation is done, but we don't find any meaningful reason to do so, because we are not modifiying configuration.

Actions #1

Updated by François ARMAND almost 9 years ago

  • Target version changed from 2.10.0~beta1 to 2.6.11
Actions #2

Updated by François ARMAND almost 9 years ago

  • Status changed from 8 to Pending technical review
  • Assignee changed from François ARMAND to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder/pull/442

Pull request here: https://github.com/Normation/rudder/pull/442

Becareful for the merge with Rudder 2.8, parameter will have to have the same modification applied.

Actions #3

Updated by François ARMAND almost 9 years ago

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

Updated by Vincent MEMBRÉ almost 9 years ago

  • Subject changed from A promise generation is issued after an archive of configuration, without any reason to An unnecesseray promise generation is launched right after amking a new archive of the configuration
Actions #6

Updated by Vincent MEMBRÉ almost 9 years ago

  • Subject changed from An unnecesseray promise generation is launched right after amking a new archive of the configuration to An unnecessary promise generation is launched right after making a new archive of the configuration
Actions #7

Updated by Vincent MEMBRÉ almost 9 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.6.11, which was released today.
Check out:

Actions

Also available in: Atom PDF