Actions
Bug #7814
closedPromise generation never finishes if jetty is restarted mid-generation
Status:
Released
Priority:
1 (highest)
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
My case: upgrade my Rudder, jetty restarts, he found new system techniques, update tech library, and start a new promise generation update. Ok, but during the promise generation jetty restarted (don't know why but it did) ;
so jetty starts ... and it's ok for him, do not need to start a promise generation and I keep my old broken promises :(
Add a flag file when we start a promise generation, and look for that flag at startup so we can launch a generation if jetty restarted during the previous one
Don't forget to wipe that file after the end of a promise generation!
Updated by Vincent MEMBRÉ almost 9 years ago
- Status changed from New to In progress
Updated by Vincent MEMBRÉ almost 9 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/1036
Updated by Vincent MEMBRÉ almost 9 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder|6cb4920e62f4d4a7ca40085d23feeb04c65f59af.
Updated by Vincent MEMBRÉ almost 9 years ago
- Status changed from Pending release to Released
Actions