Actions
Bug #10624
closed
Rudder installation docs are misleading as to running rudder-init
Pull Request:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Small
Priority:
86
Name check:
Fix check:
Regression:
Description
The current docs for a single platform, for example http://www.rudder-project.org/doc-4.1/_install_rudder_server.html#_install_rudder_root_server_on_debian_or_ubuntu, don't make it clear enought that one must run "rudder-init" at the end of the installation process.
I have myself been hit by this recently, and seen several users installing Rudder without success because that small final step was missing. This is made (much) worse by #10567.
We must clarify this in the docs ASAP. Let's just duplicate the content of http://www.rudder-project.org/doc-4.1/_install_rudder_server.html#initial-config if that's what it takes.
Updated by Jonathan CLARKE
Updated by Alexis Mousset over 7 years ago
- Status changed from New to In progress
Updated by Alexis Mousset over 7 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder-doc/pull/308
Updated by Alexis Mousset over 7 years ago
- Target version changed from 4.1.2 to 3.1.20
Updated by Alexis Mousset over 7 years ago
- Pull Request changed from https://github.com/Normation/rudder-doc/pull/308 to https://github.com/Normation/rudder-doc/pull/309
Updated by Alexis Mousset over 7 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-doc|e8beec442b138d7799b67f2038bd23ea3ee07294.
Updated by Vincent MEMBRÉ over 7 years ago
- Status changed from Pending release to Released
Actions