User story #7711
Add "Troubleshooting" section
Pull Request:
Suggestion strength:
User visibility:
Effort required:
Description
- troubleshooting workflow (rudder server debug, relevant logfiles, etc.), including an updated version of https://www.rudder-project.org/site/documentation/faq/some-reports-are-in-no-answer-for-a-node/
Subtasks
Related issues
Updated by Alexis MOUSSET about 5 years ago
- Is duplicate of User story #3818: Add a section to debug/analyze why a Node is not sending any reports added
Updated by Alexis MOUSSET about 5 years ago
- Subject changed from Add "Troubleshooting" and "Known issues" sections to Add "Troubleshooting" section
- Description updated (diff)
- Assignee set to Alexis MOUSSET
Updated by Alexis MOUSSET about 5 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis MOUSSET to Jonathan CLARKE
- Pull Request set to https://github.com/Normation/rudder-doc/pull/165
Updated by Alexis MOUSSET almost 5 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder-doc|ef30b2bcd5be75c9b065a76b896d5c19e5e5945d.
Updated by Vincent MEMBRÉ over 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.11.21, 3.0.16, 3.1.10 and 3.2.3 which were released on 2016-06-01, but not announced.
- 2.11: Changelog
- 3.0: Changelog
- 3.1: Changelog
- 3.2: Changelog
- Download: https://www.rudder-project.org/site/get-rudder/downloads/