View Issue Details

IDProjectCategoryView StatusLast Update
0000372bareos-coredirectorpublic2023-05-10 10:48
Reporterpstorz Assigned Tobruno-at-bareos  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
PlatformLinuxOSanyOS Version3
Product Version13.2.3 
Summary0000372: failing Run After Job scripts do not influence job result
DescriptionRun After Job scripts do not influence the Job Status.

When a Run After Job is configured, the job is marked as OK even when the script fails.

Obviously the local run after job is triggered AFTER the job report is already generated.
Steps To ReproduceConfigure a job that fails in the Run After Job call.e.g.

Job {
  Name = "BackupClient1"
  JobDefs = "DefaultJob"
   Run After Job = "/bin/false"
}

Job Report then says its OK:


  FD termination status: OK
  SD termination status: OK
  Termination: Backup OK


but AFTERWARDS the script fails:


04-Dez 14:26 gonzo.bareos.com-dir JobId 6: shell command: run AfterJob "/bin/false"
04-Dez 14:26 gonzo.bareos.com-dir JobId 6: Error: Runscript: AfterJob returned non-zero status=1. ERR=Child exited with code 1
TagsNo tags attached.

Relationships

related to 0000587 resolvedbruno-at-bareos joblog has "Backup Error", but jobstatus is set to successfull ('T') if writing the bootstrap file fails 

Activities

bruno-at-bareos

bruno-at-bareos

2023-05-10 10:48

manager   ~0005036

Fixed in recent version

Issue History

Date Modified Username Field Change
2014-12-04 14:28 pstorz New Issue
2015-01-23 12:04 pstorz Assigned To => pstorz
2015-01-23 12:04 pstorz Status new => assigned
2015-03-31 14:44 pstorz Assigned To pstorz =>
2015-03-31 14:44 pstorz Status assigned => confirmed
2015-12-22 16:51 joergs Relationship added related to 0000587
2023-05-10 10:48 bruno-at-bareos Assigned To => bruno-at-bareos
2023-05-10 10:48 bruno-at-bareos Status confirmed => closed
2023-05-10 10:48 bruno-at-bareos Resolution open => fixed
2023-05-10 10:48 bruno-at-bareos Note Added: 0005036