|
|
| Reporter | holtkamp | Assigned To | | |
|---|
| Priority | normal | Severity | minor | Reproducibility | always |
|---|
| Status | closed | Resolution | open | |
|---|
| Platform | Linux | OS | RHEL | OS Version | 6 |
|---|
|
|
| Summary | 0000305: catalog configuration in pool resource not honored correctly |
|---|
| Description | If you specify a catalog in the pool resource this will lead to funny results.
Fun fact: All pools will always be created in all configured catalogs... EXCEPT if you specify a catalog in the pool resource, then it will only be created in the specified catalog.
Director comes up - pools will be created in their defined catalogs or in all if none is configured
Job runs - all database entries are written to the catalog configured in the CLIENT resource and a pool record is created in that catalog (because at director startup it was only created in the catalog defined in the pool resource). |
|---|
| Steps To Reproduce | Define 2 catalogs (and don´t forget to create the database schemas, make tables and grant permissions).
Configure client resource with catalog A
Configure pool resource with catalog B
Start director
-> check both database schemas for pool records
= Pool only configured in catalog B
Run job
-> check both database schemas for job, media and pool records (and all related tables: file, filename, fileset, jobmedia, path)
= Pool suddenly exists in catalog A, all related database entries in catalog A |
|---|
| Additional Information | Tried on Version: 14.2.0 (31 May 2014)
Expected behavior: All job related database entries are written to the catalog defined in the pool resource. Catalog defined in the pool resource should have the highest authority according to the documentation.
Pool resource catalog > Job resource catalog > Client resource catalog |
|---|
| Tags | No tags attached. |
|---|
|
|
