Bug 1662447

Summary:	bacula-director dbi driver warning
Product:	[Fedora] Fedora	Reporter:	Michael Watters <wattersm>
Component:	bacula	Assignee:	Simone Caronni <negativo17>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	29	CC:	andreas, jridky, negativo17, phracek, rvokal
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-27 22:10:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Michael Watters 2018-12-28 15:27:42 UTC

Description of problem:

After upgrading to Fedora 29 the bacula-director reports an error in the systemd journal as follows.

bacula-dir[29589]: bacula-dir: dird.c:1203-0 Dbdriver field within director config file "dbi:PostgreSQL" mismatched with the Database argument "PostgreSQL" passed during Bacula compilation.

I have not made any changes to the bacula configuration and this message did not occur in Fedora 28.

Version-Release number of selected component (if applicable):

Name        : bacula-director
Version     : 9.2.1
Release     : 1.fc29
Architecture: x86_64

How reproducible:

Message occurs each time the bacula-dir service is started.

Comment 1 Michael Watters 2018-12-28 15:30:03 UTC

The same message occurs using a lowercase version of the string as well.  Here is the relevant section of the catalog configuration.

Catalog {
  Name = "bacula.example.com:postgresql"
  dbname = "bacula"; dbdriver = dbi:postgresql
    dbaddress = localhost; dbport = 5432; user = bacula; password = bacula
  }
}

Comment 2 Simone Caronni 2019-04-29 08:08:14 UTC

Have you tried just setting dbdriver = “PostgreSQL”?

Comment 3 Ben Cotton 2019-10-31 19:32:34 UTC

This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Ben Cotton 2019-11-27 22:10:06 UTC

Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.