Project

General

Profile

Bug #11418

rudder remote run cuts down IP of remote host

Added by Janos Mattyasovszky over 2 years ago. Updated almost 2 years ago.

Status:
Released
Priority:
N/A
Category:
Agent
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
30

Description

Apparently the backend cf-runagent -H <server> called via rudder remote run -a (with correct token provided) returnes the output that has the IP instead of the Hostname it is run on, example:

 10.111.111.123> -> R: @@userGroupManagement@@result_success@@<...> 

However, the awk-formatter very unluckily cuts down the last octet which is actually just the only one someone might care about:
Imageine you run this on your subnet of 192.168.0.XXX/24 and all you get in the list displayed is "192.168.0." without knowing which "XXX" you are running on... :-)

# rudder remote run -a
Start execution with config [20170921-172258-d2e89b2a]

Hostname   M| State         Technique                 Component                 Key                Message
10.111.111 E| compliant     Common                    Update                                       Policy, tools and configuration library are already up to date. No action required.
10.111.111 E| compliant     Common                    ncf Initialization                           Configuration library initialization was correct
10.111.111 E| compliant     Common                    Security parameters                          The internal environment security is acceptable
10.111.111 E| compliant     Common                    Red Button                                   Red Button is not in effect, continuing as normal...
10.111.111 E| n/a           Common                    Process checking                             Rudder agent proccesses check is done by the rudder-agent cron job
10.111.111 E| compliant     Common                    CRON Daemon      
[cut]

One'd expect to at least see all four octets of the IPv4 address (should be easy) or even better, the hostname of the node being run on (somehow harder).

#1

Updated by François ARMAND over 2 years ago

  • Target version set to 3.1.24
  • User visibility changed from First impressions of Rudder to Operational - other Techniques | Technique editor | Rudder settings
  • Priority changed from 80 to 32
#2

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 3.1.24 to 3.1.25
#3

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 3.1.25 to 387
#4

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 387 to 4.1.10
  • Priority changed from 32 to 31
#5

Updated by Benoît PECCATTE about 2 years ago

  • Status changed from New to In progress
  • Assignee set to Benoît PECCATTE
#6

Updated by Benoît PECCATTE about 2 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Benoît PECCATTE to Alexis MOUSSET
  • Pull Request set to https://github.com/Normation/rudder-agent/pull/153
#7

Updated by Rudder Quality Assistant about 2 years ago

  • Assignee changed from Alexis MOUSSET to Benoît PECCATTE
#8

Updated by Benoît PECCATTE about 2 years ago

  • Status changed from Pending technical review to Pending release
#9

Updated by Vincent MEMBRÉ almost 2 years ago

  • Status changed from Pending release to Released
  • Priority changed from 31 to 30

This bug has been fixed in Rudder 4.1.10 and 4.2.4 which were released today.

Also available in: Atom PDF