feat(gorgone): trigger nodesync on RS after config import

[vuntz]

Description

When the central Gorgone syncs configuration to a Remote Server (RS) via SENDEXPORTFILE, the RS database gets updated with new poller/server information. However, the RS's Gorgone nodes module is unaware of these changes until its next periodic resync (every 600 seconds by default). This means newly added or removed pollers behind the RS are not discovered promptly.

This PR triggers a CENTREONNODESSYNC action on the RS after the CentreonWorker import completes, so the RS immediately discovers node changes. It uses the same ADDLISTENER + callback pattern as the statistics module.

Fixes MON-194473

Type of change

• Patch fixing an issue (non-breaking change)
• New functionality (non-breaking change)
• Breaking change (patch or feature) that might cause side effects breaking part of the Software
• Updating documentation (missing information, typo...)

Target serie

• 23.10.x
• 24.04.x
• 24.10.x
• 25.10.x
• master

How this pull request can be tested ?

1. Set up a Central + Remote Server (ZMQ or SSH) with at least one poller behind the RS.
2. Add a new poller behind the RS in the Central UI.
3. Deploy the configuration to the RS (triggering SENDEXPORTFILE).
4. Check RS Gorgone logs for the following sequence:
   • [listener] add token '<worker_token>' — listener registered
   • [listener] trigger event '<worker_token>' — CentreonWorker completed
   • [legacycmd] -class- triggering nodesync after import task completion
   • [nodes] action nodesresync proceed / [nodes] Finish resync
5. Verify the newly added poller appears in the RS's proxy connections without waiting for the 600s periodic resync cycle.

Edge cases to verify:

• If CentreonWorker fails, nodesync should not be triggered (check GORGONE_ACTION_FINISH_OK guard).
• If the nodes module is not loaded on the RS, the import and broker reload should still succeed (non-fatal "unknown action" error).

Checklist

• I have followed the coding style guidelines provided by Centreon
• I have commented my code, especially new classes, functions or any legacy code modified. (docblock)
• I have commented my code, especially hard-to-understand areas of the PR.
• I have made corresponding changes to the documentation.
• I have rebased my development branch on the base branch (master, maintenance).

[coderabbitai]

Important

Review skipped

Auto reviews are limited based on label configuration.

🏷️ Required labels (at least one) (1)

• coderabbit

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch MON-194473-gorgone-nodesync-rs

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Checkmarx One – Scan Summary & Details – 3190537e-50a5-4f30-8f1b-bfcfc8da69cf

Great job! No new security vulnerabilities introduced in this pull request

[Tpo76]

🤖 This is an automatic comment generated by an internal tool.

Complexity Classification: Standard

Justification: Automatic classification failed; defaulting to standard.

Metric	Value
WIP Points	2
SLA Track	Standard SLA (2 work days)
First review SLA	1 work day

A maintainer can override this classification at any time.