User story #10314: Document remote-run exec compatibility - Rudder - Issue Tracker

Actions

Copy link

User story #10314

closed

Document remote-run exec compatibility

Added by Nicolas CHARLES almost 8 years ago. Updated almost 4 years ago.

Status:

Rejected

Priority:

N/A

Assignee:

Category:

Agent

Target version:

Ideas (not version specific)

Pull Request:

UX impact:

Suggestion strength:

User visibility:

Effort required:

Name check:

Fix check:

Regression:

Description

Remote running a 4.0 node fails, as command is not valid

root@agent1:/home/vagrant# /opt/rudder/bin/rudder agent run -uR -I -Dcfruncommand
Rudder agent 4.0.4.rc1.git201702280322 (CFEngine Core 3.7.4)
Node uuid: e04cdc24-2180-4d2e-b334-0445a13a3a45
ok: Rudder agent promises were updated.

remote running a 3.1 node fails, as command /opt/rudder/bin/rudder agent run -uR -I -Dcfruncommand --inform is not valid

root@agent2:/home/vagrant# /opt/rudder/bin/rudder agent run -uR -Dcfruncommand --inform
/opt/rudder/share/commands/agent-run : option non permise -- u
/opt/rudder/share/commands/agent-run : option non permise -- -
/opt/rudder/share/commands/agent-run : option non permise -- n
/opt/rudder/share/commands/agent-run : option non permise -- o
Rudder agent 3.1.19.rc1.git201702210714 (CFEngine Core 3.6.5)
Node uuid: 791a6ebe-cfb1-4f54-b9a2-48ca162f64b6
2017-02-28T12:38:05+0000    error: Remote execution cannot ignore lock

Option "-Dcfruncommand" is not accepted by agent in 3.1 and 4.0 (but it is ok in 4.1)

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Nicolas CHARLES almost 8 years ago

Related to Bug #10185: Remote-run exec for root fail with "rudder agent was interrupted" added

Actions

Copy link

Updated by Benoît PECCATTE almost 8 years ago

Tracker changed from Bug to User story
Subject changed from Remote-run exec fails with a 4.1 server and a 4.0 or 3.1 node to Document remote-run exec compatibility