Rudder

Hello,

Thank you for letting us know. I remember we already had cases where the distribution wasn't updated its information during an update, so perhaps it's that. But we can't ignore the possibility of a bug, of course.

So to try to know, would you mind:

- give us the version of rudder on the node and on the rudder server ?
- what is the content of cat /etc/os-release ?
- for that node, what is the date of "Inventory date" in node details summary page?
- if you run on the node "rudder agent inventory i", is there any error reported?
if now you run "rudder agent run" on the rudder root server, and go back into the node details page, summary tab: does the inventory date is updated?
- if no, would you mind running on the node:

/opt/rudder/bin/run-inventory --local=/tmp/test-inventory.ocs

And then sending us the content of /tmp/test-inventory.ocs so that we understand why the version is not correct?

Thanks, and sorry for the problem.

Hi
Thank You for answer.

Today I looked again on Rudder Server UI and I found that most of nodes with we upgraded change the OS version many of them was upgraded almost a week ago. As there is Christmas break we use this time to make OS upgrades on Ubuntu Servers.

We use Rudder Server 5.0.3.

At the moment the only one with didn't upgrade OS is the Rudder Server it self. Running rudder agent inventory:

Rudder agent 5.0.3-xenial0
Node uuid: root
Start execution with config [xxxxxxxxxxxxxxxxxxxxx]

M| State         Technique                 Component                 Key                Message
E| error         Inventory                 inventory                                    Could not execute the inventory
E| error         Inventory                 inventory                                    Generated inventory has been detected as invalid

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

Also

# /opt/rudder/bin/run-inventory --local=/tmp/test-inventory.ocs
[info] FusionInventory instance: builtin - Perl instance: system
ListUtil.c: loadable library and perl binaries are mismatched (got handshake key 0xdb00080, needed 0xde00080)

So maybe there is something wrong with my server installation.

cat /etc/os-release
NAME="Ubuntu" 
VERSION="18.04.1 LTS (Bionic Beaver)" 
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.1 LTS" 
VERSION_ID="18.04" 
HOME_URL="https://www.ubuntu.com/" 
SUPPORT_URL="https://help.ubuntu.com/" 
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" 
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" 
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic

Rudder still display:

Operating System: Ubuntu 16.04.5 LTS
Operating System Type: Linux
Operating System Name: Ubuntu
Operating System Version: 16.04
Operating System Service Pack: None
Operating System Architecture Description: x86_64

Rudder Server OS was upgraded 2 days ago.

This is minor thing but really annoying as with a lot of nodes with same Ubuntu Server it show that there is still many Servers to upgrade.

I had another similar situation on other node updated yesterday

rudder agent inventory run as compliant

Then I check /opt/rudder/bin/run-inventory --local=/tmp/test-inventory.ocs and i can see in ocs file correct OS version but on the UI of Rudder Server still is 16.04 so it seams on agent side everything is ok - Maybe the UI is simply to clearing some web cache?

Sorry for the delay, I though my collegues had updated information regarding your problem.

For the error about mismatched libraries, it seems to be related to perl version. We found these reference and we are trying to see what can be done:

- https://stackoverflow.com/questions/45000585/listutil-c-loadable-library-and-perl-binaries-are-mismatched-got-handshake-key
- https://forum.manjaro.org/t/perl-seriously-broken/29005/2

The other problem discribed in your last message isn't the same at all. Once the inventory is correctly sent to rudder server, rudder agent need to run on rudder server to take care of it (we are working to remove that horrible latency). So perhaps your agent didn't ran yet when you looked at the node page?
If it's not the case (ie if you interactively executed "rudder agent run" on the root server for example), is there any error reported? And do you see any error message in the log file /var/log/rudder/webapp/date.stderrout.log ? (you can search for the node "rudder id").

The perl error is due to the usage of an Ubuntu 16.04 package with Ubuntu 18.04. Upgrading the agent should fix it.