Actions
Bug #16850
closed
package_state_options doesn't properly defines outcome classes when called twice with same package name
Pull Request:
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
Updated by Nicolas CHARLES almost 5 years ago
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
Updated by Nicolas CHARLES almost 5 years ago
- Assignee changed from Nicolas CHARLES to Alexis Mousset
- Pull Request set to https://github.com/Normation/ncf/pull/1151
Updated by Nicolas CHARLES almost 5 years 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
Updated by Nicolas CHARLES almost 5 years ago
- Status changed from In progress to Pending technical review
Updated by Nicolas CHARLES almost 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset bb3e6ddd585a98707792792704a3aed1011c0f0f.
Updated by Nicolas CHARLES over 4 years ago
- Fix check changed from To do to Checked
Updated by Alexis Mousset over 4 years ago
- Name check changed from To do to Reviewed
Updated by Vincent MEMBRÉ over 4 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.
Updated by Alexis Mousset over 2 years ago
- Project changed from 41 to Rudder
- Category changed from Generic methods - Package Management to Generic methods
Actions