Actions
Bug #15401
closed
Factory-reset does not reset uuid and certificates
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
Description
It instead removes them, then restore them instead of creating new ones.
Updated by Alexis Mousset over 4 years ago
- Status changed from New to In progress
- Assignee set to Alexis Mousset
Updated by Alexis Mousset over 4 years ago
- Subject changed from Factory reste does not reset uuid and certificates to Factory-reset does not reset uuid and certificates
- Status changed from In progress to New
- Assignee deleted (
Alexis Mousset)
Updated by Benoît PECCATTE over 4 years ago
- Status changed from New to In progress
- Assignee set to Benoît PECCATTE
Updated by Benoît PECCATTE over 4 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/244
Updated by Benoît PECCATTE over 4 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-agent|7f912238aa742a5e98f1ac51548881283ffdc8b1.
Updated by Vincent MEMBRÉ over 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.0.0~beta1 which was released today.
Updated by François ARMAND about 4 years ago
We had a use case it seemed that during an upgrade, factory-reset script wasn't correctly updated (and so the bug was not corrected).
So if you encounter the bug in 6.0+ version, and that the node/server was updated from a Rudder 4 or 5, can you check that:
- there is not error with the factory reset command,
- in particular, that the command for UUID generation is using /opt/rudder/bin/rudder-uuid and not a system dependant one.
Actions