-
Bug
-
Resolution: Fixed
-
Minor
-
None
During a configuration reload, config_reloader worker has been interrupted.
The result is that a set of job disappeared from jenkins, and an error has been logged, but the general Jenkins state didn't change to reflect this broken state.
Shouldn't Jenkins switch to safe-restart mode on such an error, or at least warn user with a top banner message that some data have been corrupted and a restart is recommended ?
[JENKINS-11204] on failure with a configuration reload, jenkins log error but don't warn user for inconsistent state
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 141423 ] | New: JNJira + In-Review [ 189609 ] |