Bug #10448
No generation triggered at the end of installation
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Target version (plugin):
Severity:
User visibility:
Description
After installing a 4.1rc1 on CentOS6, no generation is done.
Subtasks
Associated revisions
History
#1
Updated by Alexis MOUSSET about 1 year ago
Updated by I could not find how the first generation is triggered.
#2
Updated by Alexis MOUSSET about 1 year 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.
#3
Updated by Alexis MOUSSET about 1 year ago
- Status changed from Rejected to New
#4
Updated by Alexis MOUSSET about 1 year ago
- Status changed from New to In progress
- Assignee set to Alexis MOUSSET
#5
Updated by Alexis MOUSSET about 1 year 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
#6
Updated by Alexis MOUSSET about 1 year ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-packages|651f571d1b42ced2111fc983d35fcbce1970dc15.
#7
Updated by Benoît PECCATTE about 1 year ago
Updated by - 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/
Fixes #10448: No generation triggered at the end of installation