Project

General

Profile

Actions

Bug #7814

closed

Promise generation never finishes if jetty is restarted mid-generation

Added by Vincent MEMBRÉ over 5 years ago. Updated over 5 years ago.

Status:
Released
Priority:
1
Category:
Web - Config management
Target version:
Severity:
User visibility:
Effort required:
Priority:

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!


Subtasks 1 (0 open1 closed)

Bug #7816: Fix compiling issue after merge of 7814ReleasedFrançois ARMAND2016-01-21Actions
Actions #1

Updated by Vincent MEMBRÉ over 5 years ago

  • Status changed from New to In progress
Actions #2

Updated by Vincent MEMBRÉ over 5 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
Actions #3

Updated by Vincent MEMBRÉ over 5 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions #4

Updated by Vincent MEMBRÉ over 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.11.18, 3.0.13, 3.1.6 and 3.2.0 which were released today.

Actions

Also available in: Atom PDF