Project

General

Profile

Bug #10567

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

Added by François ARMAND 7 months ago. Updated 6 months ago.

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

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

Bug #10657: Warning during compilationReleasedNicolas CHARLES

Bug #10658: Modify Rudder 404 page to speak about rudder-initReleasedFrançois ARMAND


Related issues

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 displayed Released
Related to Rudder - Bug #10430: Broken pages served by Rudder 4.1 with no explanation (missing JS/CSS due to unavailable LDAP server) Rejected

Associated revisions

Revision ab76b443
Added by François ARMAND 7 months ago

Fixes #10567: Infinite \"rudder is loading\" page if rudder-init didn't run

History

#1 Updated by François ARMAND 7 months ago

  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Getting started - demo | first install | level 1 Techniques

I'm setting the severity to "major", because if you are not accustomed to Rudder, it is very hard to understand what the problem is from the symptoms or the logs.

#2 Updated by François ARMAND 7 months ago

  • Related to Bug #1974: If an error happen during boostrap, the webapp starts but is in a zombie state and the error page is not displayed added

#3 Updated by François ARMAND 7 months ago

  • Related to Bug #10430: Broken pages served by Rudder 4.1 with no explanation (missing JS/CSS due to unavailable LDAP server) added

#4 Updated by Vincent MEMBRÉ 7 months ago

  • Target version changed from 3.1.19 to 3.1.20

#5 Updated by François ARMAND 7 months ago

  • Priority changed from 0 to 54

#6 Updated by François ARMAND 7 months ago

  • Status changed from New to In progress
  • Assignee set to François ARMAND

#7 Updated by François ARMAND 7 months ago

Since correction of #1974, we now cleanly unregister the service when there is a bootstrap check that fail. There is one which check that ALL mandatory DIT entries are present, and so that rudder-init ran.

Actually, I removed one such entry and the service return a 503:

--2017-04-25 14:36:03--  http://localhost:8080/rudder
Resolving localhost (localhost)... ::1, 127.0.0.1
Connecting to localhost (localhost)|::1|:8080... failed: Connection refused.
Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... 503 Service Unavailable
2017-04-25 14:36:03 ERROR 503: Service Unavailable.

But in https://xxx.xxx.xxx.xxx/rudder/ I'm getting the "Rudder is currently loading, please wait..." infinite page. We should have an other one for 503.

#8 Updated by François ARMAND 7 months ago

  • Status changed from In progress to New
  • Assignee deleted (François ARMAND)

#9 Updated by François ARMAND 7 months ago

Regarding the previous message, on Rudder 3.1, when loading we have the following return:

--2017-04-25 15:05:35--  http://localhost:8080/rudder
Resolving localhost (localhost)... ::1, 127.0.0.1
Connecting to localhost (localhost)|::1|:8080... failed: Connection refused.
Connecting to localhost (localhost)|127.0.0.1|:8080... failed: Connection refused.

#10 Updated by Alexis MOUSSET 7 months ago

When Rudder is loading, jetty does not answer, and apache returns a 503 too.

We can at least modify the "loading" message to include a reminder about rudder-init.

#11 Updated by François ARMAND 7 months ago

  • Subject changed from There is no clear warning if rudder-init didn't run (and webapp is broken) to Infinite "rudder is loading" page is rudder-init didn't run

#12 Updated by François ARMAND 7 months ago

  • Subject changed from Infinite "rudder is loading" page is rudder-init didn't run to Infinite "rudder is loading" page if rudder-init didn't run

#13 Updated by François ARMAND 7 months ago

  • Status changed from New to In progress
  • Assignee set to François ARMAND

#14 Updated by François ARMAND 7 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder/pull/1646

#15 Updated by François ARMAND 7 months ago

  • Status changed from Pending technical review to Pending release

#16 Updated by Vincent MEMBRÉ 6 months ago

  • 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