View Issue Details

IDProjectCategoryView StatusLast Update
0000372bareos-coredirectorpublic2015-12-22 16:51
Reporterpstorz Assigned To 
Status confirmedResolutionopen 
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 JobId 6: shell command: run AfterJob "/bin/false"
04-Dez 14:26 JobId 6: Error: Runscript: AfterJob returned non-zero status=1. ERR=Child exited with code 1
TagsNo tags attached.
bareos-master: impact
bareos-master: action
bareos-19.2: impact
bareos-19.2: action
bareos-18.2: impact
bareos-18.2: action
bareos-17.2: impact
bareos-17.2: action
bareos-16.2: impact
bareos-16.2: action
bareos-15.2: impact
bareos-15.2: action
bareos-14.2: impact
bareos-14.2: action
bareos-13.2: impact
bareos-13.2: action
bareos-12.4: impact
bareos-12.4: action


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


There are no notes attached to this issue.

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