Skip to content

fix(apps::backup::veeam): fix job-type and session values - CTOR-2490 - #6353

Open
itoussies wants to merge 1 commit into
developfrom
CTOR-2490-plugin-apps-backup-veeam-local-plugin-job-status-job-type-and-session-result-are-null-with-veeam-13-power-shell-7
Open

fix(apps::backup::veeam): fix job-type and session values - CTOR-2490#6353
itoussies wants to merge 1 commit into
developfrom
CTOR-2490-plugin-apps-backup-veeam-local-plugin-job-status-job-type-and-session-result-are-null-with-veeam-13-power-shell-7

Conversation

@itoussies

@itoussies itoussies commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Refs:CTOR-2490

Centreon team (internal PR)

Description

With Veeam Backup & Replication 13 or inferior, the job-status mode of apps::backup::veeam::local::plugin returns type: unknown and status: - for every job, and therefore reports CRITICAL on all of them regardless of the actual backup outcome.

The PowerShell script embedded in the plugin reads the job type and the session result through the .value accessor:

$item.type = $_.JobType.value
$session.result = $_.Result.value

This should be (as before last change)

$item.type = $_.JobType.value__
$session.result = $_.Result.value__

Fixes CTOR-2490

Type of change

  • Patch fixing an issue (non-breaking change)
  • New functionality (non-breaking change)
  • Functionality enhancement or optimization (non-breaking change)
  • Breaking change (patch or feature) that might cause side effects breaking part of the Software

How this pull request can be tested ?

Please describe the procedure to verify that the goal of the PR is matched.
Provide clear instructions so that it can be correctly tested.
Mention the automated tests included in this FOR (what they test like mode/option combinations).

Checklist

  • I have followed the coding style guidelines provided by Centreon
  • I have commented my code, especially hard-to-understand areas of the PR.
  • I have rebased my development branch on the base branch (develop).
  • In case of a new plugin, I have created the new packaging directory accordingly.
  • I have implemented automated tests related to my commits.
    • Data used for automated tests are anonymized.
  • I have reviewed all the help messages in all the .pm files I have modified.
    • All sentences begin with a capital letter.
    • All sentences end with a period.
    • I am able to understand all the help messages, if not, exchange with the PO or TW to rewrite them.
  • After having created the PR, I will make sure that all the tests provided in this PR have run and passed.

@itoussies
itoussies requested a review from a team as a code owner August 13, 2026 10:48
@itoussies
itoussies requested review from Evan-Adam and removed request for a team August 13, 2026 10:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant