According to kern:
This seems to me to be a normal behavior for Bacula rather than a bug.
As far as I can determine, the first job actually created the Volume in
the catalog before it failed, thus any subsequent job is going to use
that Volume without invoking any variable expansion, which apparently is
what happened because the second job found the volume, labeled it, then
continued as you indicated.
** Changed in: bacula (Ubuntu)
Status: Triaged => Invalid
--
variable expansion uses outdated data
https://bugs.launchpad.net/bugs/459573
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bacula in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
