Bug #18303
closed
Calling the relay-api to trigger a remote run on all nodes do an infinite loop on root server, killing it
Added by Nicolas CHARLES about 4 years ago.
Updated about 4 years ago.
Category:
Relay server or API
Files
Problem is that root is both a next hop and a neighbor
DEBUG relayd::api::remote_run: Starting remote run (asynchronous: false, keep_output: true)
DEBUG relayd::api::remote_run: Neighbors: [
"relay",
"server.rudder.local",
"agent2.rudder.local",
]
DEBUG relayd::api::remote_run: Remote run command: '"sudo" "/opt/rudder/bin/rudder" "remote" "run" "relay,server.rudder.local,agent2.rudder.local"'
DEBUG relayd::api::remote_run: Next-hops: [
(
"server.rudder.local",
All,
),
(
"relay",
All,
),
]
- Status changed from New to In progress
- Assignee set to Alexis Mousset
- Subject changed from calling the relay-api to trigger a remote run on all nodes do an infinite loop on root server, killing it to Calling the relay-api to trigger a remote run on all nodes do an infinite loop on root server, killing it
- 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/pull/3246
- Status changed from Pending technical review to Pending release
- Name check changed from To do to Reviewed
- Fix check changed from To do to Checked
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.1.6 and 6.2.0~beta1 which were released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by