Project

General

Profile

Actions

Bug #10567

closed

Infinite "rudder is loading" page if rudder-init didn't run

Added by François ARMAND about 7 years ago. Updated about 7 years ago.

Status:
Released
Priority:
N/A
Category:
System integration
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Priority:
54
Name check:
Fix check:
Regression:

Description

If rudder-init is not run for reason, the webapp can't run (init data are not set). So it's completly broken, leading to #1974 (which is particulary bad with #10430).
We need to display a clean error message to the user in that case.


Subtasks 2 (0 open2 closed)

Bug #10657: Warning during compilationReleasedNicolas CHARLESActions
Bug #10658: Modify Rudder 404 page to speak about rudder-initReleasedFrançois ARMANDActions

Related issues 3 (0 open3 closed)

Related to Rudder - Bug #1974: If an error happen during boostrap, the webapp starts but is in a zombie state and the error page is not displayedReleasedNicolas CHARLESActions
Related to Rudder - Bug #10430: Broken pages served by Rudder 4.1 with no explanation (missing JS/CSS due to unavailable LDAP server)RejectedActions
Related to Rudder - Bug #15387: Clean-up Jetty abort on bootReleasedVincent MEMBRÉActions
Actions

Also available in: Atom PDF