Bug #10658
closed
Bug #10567: Infinite "rudder is loading" page if rudder-init didn't run
Modify Rudder 404 page to speak about rudder-init
Added by François ARMAND over 6 years ago.
Updated over 6 years ago.
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Very Small
Description
With the parent ticket corrected, we are now reaching Rudder 404 page when the rudder-init script wasn't executed before first run. We need to remind user to do in the "this may be caused by" list.
- Severity changed from Major - prevents use of part of Rudder | no simple workaround to Minor - inconvenience | misleading | easy workaround
I'm setting the severity to "major" because when you have that page, it is likelly that you are going to look to the logs, but the log only talk about missing entries / problem loading, not the fact that the cause is likelly to be that the user didn't ran rudder-init.
- Priority changed from 0 to 53
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from Raphael GAUTHIER to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/1648
- Status changed from Pending technical review to Pending release
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.1.20, 4.0.5 and 4.1.2 which were released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by Anonymous 
Updated by