if [[ $(cat /var/rudder/local/properties.d/role.json | grep use$sgbd | cut -d : -f2 | cut -d , -f1) == true ]]; then echo $sgbd; else exit 1 fi
/opt/rudder/bin/run-inventory --local=/var/rudder/tmp/inventory/prod-c2d09dd7-a6d8-4eec-8812-297506ff2a92.ocs [info] FusionInventory instance: builtin Encode.c: loadable library and perl binaries are mismatched (got handshake key 0xce00080, needed 0xed00080)
I've updated my Rudder server from 6.2 to 7.1. I've done this by updating the repository and then ran:
zypper up rudder-server-root rudder-server-relay rudder-reports rudder-webapp rudder-agent
Upgrade went fine, no errors reported etc. There is however now one issue. The compliance of the nodes dropped from 100% to 0%. When checking on the individual nodes they all report this error: "No recent reports have been received for this node in the grace period since the last configuration policy change."
So as a test on some of the nodes I changed some resources managed by Rudder and ran the agent. And that ran without any problem at all. Everything was corrected by Rudder as expected.
As I figured that maybe this was due to the 6.2 version of the agent still runnnig on the nodes, I upgraded that on some of them as well to 7.1. Still no luck.
Then I thought that maybe it needed some time to update the reports again. But it has been over 4 hours by now and I'm still at 0% compliance.
I'm running this on SLES15 SP3. I took a snapshot of the VM running the Rudder server before the upgrade, so I could revert back to that. (If I haven't solved it by Monday I guess it will come to that), but I prefer not to do this. So if someone could help me fix this, that would be greatly appreciated.