Actions
Bug #21279
closed
relayd error messages about config files are lacking path information
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
Description
INFO rudder_relayd: Starting rudder-relayd 7.1.1 INFO rudder_relayd: Read configuration from "/opt/rudder/etc/relayd/" INFO rudder_relayd::data::node: Parsing nodes list from "/var/rudder/lib/relay/nodeslist.json" INFO rudder_relayd::data::node: Nodes list file does not exist, considering it as empty WARN rudder_relayd::data::node: certificate for unknown node: root ERROR rudder_relayd: No such file or directory (os error 2)
we need to provide relevant context and display it.
Updated by Alexis Mousset almost 2 years ago
- Status changed from New to In progress
- Assignee set to Alexis Mousset
Updated by Alexis Mousset almost 2 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Félix DALLIDET
- Pull Request set to https://github.com/Normation/rudder/pull/4331
Updated by Alexis Mousset almost 2 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|0ce884444f62ac1241f344a017f6ac98c586c5a2.
Updated by Alexis Mousset almost 2 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ almost 2 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.1.2 which was released today.
Actions