Bug #13882: rudder agent inventory wrongly states that we are not in full compliance mode - Rudder - Issue Tracker

Actions

Copy link

Bug #13882

closed

rudder agent inventory wrongly states that we are not in full compliance mode

Bug #13882: rudder agent inventory wrongly states that we are not in full compliance mode

Added by Nicolas CHARLES about 7 years ago. Updated almost 7 years ago.

Status:

Released

Priority:

N/A

Assignee:

Alexis Mousset

Category:

Agent

Target version:

4.3.9

Pull Request:

https://github.com/Normation/rudder-a...

Severity:

UX impact:

User visibility:

First impressions of Rudder

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

Running rudder agent inventory, I get the following output

Rudder agent 4.3.7.rc1.git201811200148
Node uuid: a5c27396-19c6-4d9a-99da-c9ca3b9f2132
Start execution with config [20181121-092358-b3b3be7a]

M| State         Technique                 Component                 Key                Message
E| compliant     Inventory                 inventory                                    The inventory has been successfully sent

## Summary #####################################################################
Not all components were displayed because we are not in full compliance mode. Please run with -g to force full compliance mode.
   => 1 components in Enforce mode
      -> 1 compliant
Execution time: 3.15s
################################################################################

it is in full compliance, so we should not state that

Related issues 1 (0 open — 1 closed)

Updated by Nicolas CHARLES about 7 years ago Actions
Copy link
#1

reason is rudder agent inventory calls rudder agent run D force_inventory -b doInventory - so we have a partial run execution
option -b set FULL_COMPLIANCE to 0, which is not what we wish

we should detect that we are in partial run, and in this case clearly state it "run is not complete due to command line argument" or something like that