Project

General

Custom queries

Profile

Actions
Copy link

Bug #16850

closed

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

Added by Nicolas CHARLES over 5 years ago. Updated about 3 years ago.

Status:
Released
Priority:
N/A
Assignee:
Alexis Mousset
Category:
Generic methods
Target version:
5.0.17
Pull Request:
https://github.com/Normation/ncf/pull...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Checked
Regression:

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 1 (0 open — 1 closed)

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
Actions
Copy link
 #2

Updated by Nicolas CHARLES over 5 years ago

  • Assignee changed from Nicolas CHARLES to Alexis Mousset
  • Pull Request set to https://github.com/Normation/ncf/pull/1151
Actions
Copy link
 #5

Updated by Nicolas CHARLES over 5 years ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ about 5 years 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.

Actions
Copy link

Also available in: Atom PDF