So, clearly, this is something like #19920. When I reproduced it, my inventory was processed, and rudder was shut down before being saved:
[2022-05-11 10:36:38+0200] INFO inventory-processing - Watch new inventory file 'server-root.ocs' with signature available: process.
[2022-05-11 10:36:40+0200] INFO policy.generation - No node configuration was updated, no policies to write
[2022-05-11 10:36:40+0200] DEBUG explain_compliance - Updated node configuration ids:
2022-05-11 10:36:43.577:INFO:oejs.AbstractConnector:JettyShutdownThread: Stopped ServerConnector@36d697ab{HTTP/1.1, (http/1.1)}{127.0.0.1:8080}
2022-05-11 10:36:43.577:INFO:oejs.session:JettyShutdownThread: node0 Stopped scavenging
2022-05-11 10:36:43.598:INFO:oejshC.rudder:JettyShutdownThread: Closing Spring root WebApplicationContext
2022-05-11 10:36:43.683:INFO:oejsh.ContextHandler:JettyShutdownThread: Stopped o.e.j.w.WebAppContext@7a765367{/rudder,null,STOPPED}{/opt/rudder/share/webapps/rudder.war}
--- EOF ---
It was not processed in next reboot, so it is likely similar than #19920: moved before being saved.
But then, just trying to do an other rudder agent inventory
did not trigger its parsing, and inventory was just sitting in directory /var/rudder/inventories/accepted-nodes-updates
.
Touching the inventory file did trigger its processing.
And now, new rudder agent inventory
does lead to a instant processing of inventory.
And stopping rudder, putting inventory in directory, starting rudder does lead to a correct processing.
Not sure what is going on.