Actions
Bug #16760
closed
Remote run always timeout for nodes behing relays
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
52
Name check:
Reviewed
Fix check:
Checked
Regression:
Description
After #16448 correction, I can contact and get results for root server and nodes directly behing it.
But when I try to contact a node behind a relay, I get a timeout.
I also tried to directly contact remote run api and also get a timeout, so the problem seems to be elsewhere.
Updated by François ARMAND about 4 years ago
- Related to Bug #16448: Trigger remote run in node details says it timeouts added
Updated by Alexis Mousset about 4 years ago
- Status changed from New to In progress
- Assignee set to Alexis Mousset
Updated by Alexis Mousset about 4 years ago
- Assignee changed from Alexis Mousset to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder/pull/2779
Updated by Alexis Mousset about 4 years ago
- Status changed from In progress to Pending release
Applied in changeset rudder|952e82f0f169934f7fd4249fa6ef41d4c0c7262a.
Updated by François ARMAND about 4 years ago
- Target version changed from 6.0.4 to 6.0.3
Updated by François ARMAND about 4 years ago
- Fix check changed from To do to Checked
Updated by Alexis Mousset about 4 years ago
- Name check changed from To do to Reviewed
Updated by Vincent MEMBRÉ about 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.0.3 which was released today.
Actions