Project

General

Profile

Actions
Copy link

Bug #11318

closed

rudder remote run error, and unable to pass -i option

Added by Florian Heigl almost 8 years ago. Updated over 6 years ago.

Status:
Released
Priority:
N/A
Assignee:
Nicolas CHARLES
Category:
Agent
Target version:
4.1.17
Pull Request:
https://github.com/Normation/rudder-a...
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

I was trying to look into the following error from "rudder remote"

@rudder-master:/root # rudder remote run client.domain.tld
error Rudder agent was interrupted during execution by a fatal error
Run with -i to see log messages.

  1. Summary #####################################################################
    0 components verified in 1 directives
    execution time: 0.67s
    ################################################################################@

I could see in tcpdump my master is calling out to the end system so I was uncertain if it did something or not.
To provoke more work on the remote side, I gave -Dforce_inventory, and then added -i which seems to not work like that.

@rudder-master:/root # rudder remote run client.domain.tld -Dforce_inventory
error Rudder agent was interrupted during execution by a fatal error
Run with -i to see log messages.

  1. Summary #####################################################################
    0 components verified in 1 directives
    execution time: 0.68s ################################################################################
    rudder-master:/root # rudder remote run client.domain.tld -Dforce_inventory -i
    error Rudder agent was interrupted during execution by a fatal error
    Run with -i to see log messages.
  1. Summary #####################################################################
    0 components verified in 1 directives
    execution time: 0.67s ################################################################################
    rudder-master:/root # rudder remote run client.domain.tld -i -Dforce_inventory
    error Rudder agent was interrupted during execution by a fatal error
    Run with -i to see log messages.
  1. Summary #####################################################################
    0 components verified in 1 directives
    execution time: 0.68s ################################################################################
    rudder-master:/root # rudder remote run -i client.domain.tld -Dforce_inventory
    Usage rudder remote run <node_ip_or_name>@

I tried read hard to get proper formatting on this but it seems redmine does hate me, so I'll just leave it as it is.

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #13897: Command "rudder remote run" must accept "-a -t" RejectedActions
Actions
Copy link
 #1

Updated by Florian Heigl almost 8 years ago

4.1.5 Agent

Actions
Copy link
 #2

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version set to 4.1.7
  • User visibility set to Operational - other Techniques | Technique editor | Rudder settings
  • Priority changed from 0 to 32

Does this error happen on all your nodes or just this one ?

Actions
Copy link
 #3

Updated by Florian Heigl almost 8 years ago

Hi,

the error was on multiple, but the report is about that -i doesn't work :)

Actions
Copy link
 #4

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 4.1.7 to 4.1.8
Actions
Copy link
 #5

Updated by François ARMAND almost 8 years ago

Hi,

There seems to be technical limit on CFEngine "remote run" implementation for now... It seems deep rooted and may be difficult to correct.

Thanks for reporting!

Actions
Copy link
 #6

Updated by Florian Heigl almost 8 years ago

Again: The issue is about the parser issue that -i does not work if you give -D

Actions
Copy link
 #7

Updated by Benoît PECCATTE almost 8 years ago

The problem is as follow:
  • when using -Dforce_inventory there is no report thats is done (which is expected)
  • missing reports are incorrectly detected because of #9807
  • missing reports trigger a message "run with -i"
  • running with -i does not give as many log remotely as locally
So :
  • -i does not give expected result with remote-run because of cfengine limitation
  • in this case there is no real error and no need to run with -i
Actions
Copy link
 #8

Updated by Florian Heigl almost 8 years ago

We found that remote-run does not have the UPDATE_OPTIONS variable, whereas agent-run does have it.
So this seems to be an issue with the option parser, probably the one in agent-run is a tad newer than the one in remote-run.

Actions
Copy link
 #9

Updated by Vincent MEMBRÉ almost 8 years ago

  • Status changed from New to In progress
  • Assignee set to Vincent MEMBRÉ
Actions
Copy link
 #10

Updated by Benoît PECCATTE over 7 years ago

The UPDATE_OPTIONS in "rudder agent run" are used to pass options to "rudder agent update" when -u is used.
"rudder remote run" does not have an option to force update remotely (it just does it)

Actions
Copy link
 #11

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 4.1.8 to 4.1.9
Actions
Copy link
 #12

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 4.1.9 to 4.1.10
  • Priority changed from 32 to 31
Actions
Copy link
 #13

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 4.1.10 to 4.1.11
  • Priority changed from 31 to 30
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 4.1.11 to 4.1.12
  • Priority changed from 30 to 29
Actions
Copy link
 #15

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 4.1.12 to 4.1.13
Actions
Copy link
 #16

Updated by Benoît PECCATTE about 7 years ago

  • Target version changed from 4.1.13 to 411
Actions
Copy link
 #17

Updated by Benoît PECCATTE about 7 years ago

  • Target version changed from 411 to 4.1.13
Actions
Copy link
 #18

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 4.1.13 to 4.1.14
  • Priority changed from 29 to 28
Actions
Copy link
 #19

Updated by Benoît PECCATTE almost 7 years ago

  • Target version changed from 4.1.14 to 4.1.15
  • Priority changed from 28 to 27
Actions
Copy link
 #20

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.15 to 4.1.16
Actions
Copy link
 #21

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.16 to 4.1.17
Actions
Copy link
 #22

Updated by Nicolas CHARLES over 6 years ago

  • Priority changed from 27 to 0

i've been testing the remote run command, and it's been painfully hard (on centos7, rudder 4.1.17)
The order of argument is important
Ok:

rudder remote run -ait RzZX185IOUGHBGS0Xfy7LpBx6VyIxjSD

NOK: no token found

rudder remote run -a -t RzZX185IOUGHBGS0Xfy7LpBx6VyIxjSD

NOK: no target found

rudder remote run  -t RzZX185IOUGHBGS0Xfy7LpBx6VyIxjSD  -a

we should at least fix the doc, but using workable options is a necessity

Actions
Copy link
 #23

Updated by Benoît PECCATTE over 6 years ago

  • Assignee changed from Vincent MEMBRÉ to Benoît PECCATTE
Actions
Copy link
 #24

Updated by Benoît PECCATTE over 6 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Benoît PECCATTE to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder-agent/pull/197
Actions
Copy link
 #25

Updated by Benoît PECCATTE over 6 years ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #26

Updated by Vincent MEMBRÉ over 6 years ago

  • Status changed from Pending release to Released
This bug has been fixed in Rudder 4.1.17, 4.3.7 and 5.0.3 which were released today. 
Changelog
 Changelog
 Changelog
Actions
Copy link
 #27

Updated by Benoît PECCATTE over 6 years ago

  • Related to Bug #13897: Command "rudder remote run" must accept "-a -t" added
Actions
Copy link

Also available in: Atom PDF