Project

General

Profile

Actions

User story #6313

closed

Rudder 3.0 node info misses the "current report version identifier"

Added by François ARMAND almost 10 years ago. Updated about 8 years ago.

Status:
Rejected
Priority:
1 (highest)
Category:
Web - Config management
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

In Rudder 3.0 and up, each node get an expected report identifier that is transmitted in the log_info "end run" report.

But nowhere in the interface can we get that information, one has to go to /var/rudder/share/${nodeid}/rules/cfengine-community/common/1.0/site.cf and search for "rudder_node_config_id" string => "xxxx"; to know what it it.

And to get the last 3 with their dates, one has to query the database :(


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #6311: Missing reports when editing twice the same file with enforce a file content v7.0ReleasedNicolas CHARLES2015-03-02Actions
Actions #1

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 3.0.2 to 3.0.3
Actions #2

Updated by François ARMAND almost 10 years ago

  • Tracker changed from Bug to User story
  • Description updated (diff)
Actions #3

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 3.0.3 to 3.0.4
Actions #4

Updated by Benoît PECCATTE over 9 years ago

  • Status changed from 8 to New
Actions #5

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 3.0.4 to 3.0.5
Actions #6

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 3.0.5 to 3.0.6
Actions #7

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 3.0.6 to 3.0.7
Actions #8

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 3.0.7 to 3.0.8
Actions #9

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 3.0.8 to 3.0.9
Actions #10

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 3.0.9 to 3.0.10
Actions #11

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 3.0.10 to 3.0.11
Actions #12

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 3.0.11 to 3.0.12
Actions #13

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 3.0.12 to 3.0.13
Actions #14

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 3.0.13 to 3.0.14
Actions #15

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 3.0.14 to 3.0.15
Actions #16

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.0.15 to 3.0.16
Actions #17

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.0.16 to 3.0.17
Actions #18

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.0.17 to 302
Actions #19

Updated by Alexis Mousset over 8 years ago

  • Target version changed from 302 to 3.1.12
Actions #20

Updated by Alexis Mousset over 8 years ago

The lastest config id is now displayed in the reports tab.

Actions #21

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.1.12 to 3.1.13
Actions #22

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.1.13 to 3.1.14
Actions #23

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions #24

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions #25

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions #26

Updated by François ARMAND about 8 years ago

  • Status changed from New to Rejected

This is no more the case in 3.1 and up. The version is reported in the "reports" tab on the summary zone, and in comand line on the agent when "rudder agent run" is exec for example.

Actions

Also available in: Atom PDF