[pkg-bacula-devel] Bug#1000176: bacula-director-pgsql: setup suggests no password and then rejects it

[Ross Boylan]

Package: bacula-director-pgsql
Version: 9.4.2-2+deb10u1
Severity: normal

Dear Maintainer,

   * What led up to the situation?
   My 2nd attempt to install bacula after initial failure of
   Bug#1000174.
   Because of that, configuration asks lower-priority questions.
   I requested password based login and gave a FQDN for the PG server.
   I get to this screen
 │ Please provide the password for the postgres account with which this package should perform administrative actions.       │ 
 │                                                                                                                           │ 
 │ For a standard PostgreSQL installation, a database password is not required, since authentication is done at the system   │ 
 │ level.                                                                                                                    │ 
 │                                                                                                                           │ 
 │ Password of your database's administrative user:
  
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   Left the password field blank.  That's my only choice, since I
   never set it during PG setup (that is, when I installed PG, months
     ago).  I hit OK. 
   
   * What was the outcome of this action?
   | Empty passwords unsupported with PostgreSQL |
   with the only choice being OK, which takes me back to prior screen.

   * What outcome did you expect instead?
   That the configuration would accept my omission of the password
   since the earlier step recommended it!  And that the omission
   would be possible, since I do have the standard setup in which it
   is not set.

Comment: The host name I set for the PG database is an alias for the
same machine on which I'm installing bacula.  It's unclear to me if
that will confuse the installer and subsequent operations about
whether it's the same.  I did accept the default tcp/ip communication
with the database.

Next step: I'm not sure.  Several alternatives:
1. tell the setup not to use dbconfig and clean things up afterward.
2. enter a bogus password to get past this step and hope it will be
ignored.
3. set a real password for the postgres user and then enter that.


-- System Information:
Debian Release: 10.11
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-18-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages bacula-director-pgsql depends on:
iu  bacula-common-pgsql                       9.4.2-2+deb10u1
iu  dbconfig-pgsql                            2.0.11+deb10u1
ii  debconf [debconf-2.0]                     1.5.71+deb10u1
iu  postgresql-client                         11+200+deb10u4
ii  postgresql-client-11 [postgresql-client]  11.14-0+deb10u1

Versions of packages bacula-director-pgsql recommends:
ii  postgresql  11+200+deb10u4

Versions of packages bacula-director-pgsql suggests:
ii  gawk  1:4.2.1+dfsg-1

-- no debconf information