Actions
Bug #11234
closedBug #10766: rudder agent factory-reset bugs
rudder agent factory-reset bugs
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Updated by Benoît PECCATTE about 7 years ago
- Status changed from New to In progress
- Assignee set to Benoît PECCATTE
Updated by Benoît PECCATTE about 7 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Benoît PECCATTE to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-agent/pull/127
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 4.1.6 to 4.1.7
Updated by Benoît PECCATTE about 7 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-agent|c0663fd40e43120ffe0a5a33cef6b47d05f23416.
Updated by Nigel Mundy about 7 years ago
The issue that this parent's bug report was for included the -f (force) switch not working. It was allegedly fixed in 4.1.6 but has not been, and the above changeset is still showing the issue.
It needs the addition of a valid selection for "f" to the getopts line in agent-factory-reset, ie:
+while getopts "iIvdqcf" opt; do
-while getopts "iIvdqc" opt; do
case $opt in
i|I|v|d)
VERBOSE=true
QUIET=false
;;
q)
VERBOSE=false
QUIET=true
;;
c)
clear_colors
;;
f)
FORCE=1
;;
esac
Updated by Vincent MEMBRÉ about 7 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.1.7 and 4.2.0~rc1 which were released today.
- 4.1.7: Announce Changelog
- 4.2.0~rc1: Announce Changelog
- Download: https://www.rudder-project.org/site/get-rudder/downloads/
Actions