Actions
Bug #10448
closed
No generation triggered at the end of installation
Bug #10448:
No generation triggered at the end of installation
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
After installing a 4.1rc1 on CentOS6, no generation is done.
Updated by Alexis Mousset almost 9 years ago
I could not find how the first generation is triggered.
Updated by Alexis Mousset over 8 years ago
- Description updated (diff)
- Status changed from New to Rejected
It only happened on rc1, could not reproduce with nightly. Closing for now, if it happens again, we will reopen the ticket.
Updated by Alexis Mousset over 8 years ago
- Status changed from Rejected to New
Updated by Alexis Mousset over 8 years ago
- Status changed from New to In progress
- Assignee set to Alexis Mousset
Updated by Alexis Mousset over 8 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-packages/pull/1309
Updated by Alexis Mousset over 8 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-packages|651f571d1b42ced2111fc983d35fcbce1970dc15.
Updated by Benoît PECCATTE over 8 years ago
- Status changed from Pending release to Released
- Priority set to 0
This bug has been fixed in Rudder 4.1.0 which was released today.
- 4.1.0: Announce Changelog
- Download: https://www.rudder-project.org/site/get-rudder/downloads/
Actions