"Job not run" message after any attempt to run a job using bconsole
Bug #1004494 reported by
Evgeniy
This bug affects 7 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bacula (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
"Job not run" message after any attempt to run a job using console.
A job still can be run if run like:
* run job=jobname yes
Steps To Reproduce * run
It shows me the job parameters and asks: yes/mod/no?
Whether I enter yes or mod, it answers me "Job not run".
Additional Information The problem may be related to the director or to the bconsole.
I cannot run a job using bat too because of a bat's bug.
I filed the bug here: http://
and got the decision that the bug is because of a bad build and it is not present in the main source tree.
Changed in bacula (Ubuntu): | |
status: | Expired → Incomplete |
To post a comment you must log in.
Thanks for submitting this bug. (Note I can't look at the bugs.bacula.org without signing up for an account.)
To be clear, you are saying that
run job=jobname yes
succeeds, and is a usable workaround?