Project

General

Profile

Bug #16850

package_state_options doesn't properly defines outcome classes when called twice with same package name

Added by Nicolas CHARLES 3 months ago. Updated about 1 month ago.

Status:
Released
Priority:
N/A
Category:
Generic methods - Package Management
Target version:
Severity:
User visibility:
Effort required:
Priority:
0

Description

i we want to enforce that a package is there, and upgrade it on a second call, package_state_options won't define properly classes has ncf_package_${canonified_state}_${canonified_name} is not precise enough


Related issues

Related to Rudder - Bug #16849: When using twice directive packageManagement 1.2, once to ensure presence of a package, and second one to upgrade the package, reporting and posthook is wrong on the second oneReleasedBenoît PECCATTEActions
#1

Updated by Nicolas CHARLES 3 months ago

  • Status changed from New to In progress
  • Assignee set to Nicolas CHARLES
#2

Updated by Nicolas CHARLES 3 months ago

  • Assignee changed from Nicolas CHARLES to Alexis MOUSSET
  • Pull Request set to https://github.com/Normation/ncf/pull/1151
#3

Updated by Nicolas CHARLES 3 months ago

  • Related to Bug #16849: When using twice directive packageManagement 1.2, once to ensure presence of a package, and second one to upgrade the package, reporting and posthook is wrong on the second one added
#4

Updated by Nicolas CHARLES 3 months ago

  • Status changed from In progress to Pending technical review
#5

Updated by Nicolas CHARLES 3 months ago

  • Status changed from Pending technical review to Pending release
#8

Updated by Vincent MEMBRÉ about 1 month ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 5.0.17 and 6.0.5 which were released today.

Also available in: Atom PDF