[Bug 1840485] Re: Eoan autopkgtest regressions - Migration Excuses

[Robie Basak]

Hi Rafael,

Thank you for working on this!

I see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933019 for the
glusterfs issue, making this FTBFS in sid. There's also
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922344 for an
autopkgtest regression. I'm not sure if that's the same issue as the one
you're fixing here, but I think Debian also currently has your failure.

I suppose the dropping of glusterfs support is a feature change, but
bareos isn't currently in the Eoan release pocket at all right now.

Is this worth doing all this disabling in Ubuntu right now, or would it
be better to leave it for Debian to fix for possible inclusion in Ubuntu
next cycle? Is it worth the delta, the risk of introducing broken not-
Postgres support (due to it now being untested), without Debian's
support (since they have this version of the package stuck in unstable),
and with the ongoing maintenance burden for Ubuntu?

Some minor notes on your debdiff in case we decide to continue:

+  * Disable glusterfs support due to API changes
+  * Disable MySQL/SQLite DEP8 due to bad tests (LP: #1840485)

This makes it look like LP: #1840485 doesn't relate to "Disable
glusterfs support" but it does. You could adjust the changelog entry to
make this clear, but it's also difficult to link this bug to the Debian
glusterfs bug so perhaps this bug needs splitting into two?

It's a useful technique when experimenting, but please avoid "commenting
out" in final uploads. I see this as unnecessary cruft that others are
forced to read through later, though I'm interested to hear if others
disagree. The changelog will record that you removed those lines, and we
can use a VCS, or simply debdiffs, if we want to restore them again
later.

** Bug watch added: Debian Bug tracker #933019
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933019

** Bug watch added: Debian Bug tracker #922344
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922344

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1840485

Title:
  Eoan autopkgtest regressions - Migration Excuses

Status in bareos package in Ubuntu:
  In Progress

Bug description:
  bareos mysql-all test is failing. This happens because the way the
  mysql test has been written. It looks like that, during
  reconfiguration, the database-type is reset to pgsql, instead of
  sticking to mysql like it should:

  ---- SCRIPT

  Tests: mysql-all
  Restrictions: needs-root allow-stderr
  Depends:
   bareos,
   bareos-database-mysql,
   default-mysql-server | virtual-mysql-server,

  ---- SCRIPT

  #!/bin/sh

  set -e

  # reinstall database in case mysql wasn't started early enough

  service mysql start

  echo 'bareos-database-common bareos-database-common/database-type string mysql' | debconf-set-selections
  echo 'bareos-database-common bareos-database-common/database-type seen true' | debconf-set-selections
  echo 'bareos-database-common bareos-database-common/dbconfig-reinstall boolean true' | debconf-set-selections
  echo 'bareos-database-common bareos-database-common/dbconfig-reinstall seen true' | debconf-set-selections

  dpkg-reconfigure bareos-database-common    <---- HERE the database-
  type is reset

  service bareos-dir restart

  test/all

  ---- REPRODUCER

  (c)root at tests:~$ echo 'bareos-database-common bareos-database-common
  /database-type string mysql' | debconf-set-selections

  --

  (c)root at tests:~$ echo 'bareos-database-common bareos-database-common
  /database-type seen true' | debconf-set-selections

  --

  (c)root at tests:~$ debconf-show bareos-database-common | grep database-type
  * bareos-database-common/database-type: mysql

  --

  (c)root at tests:~$ DEBIAN_FRONTEND=noninteractive dpkg-reconfigure bareos-database-common
  (config) dbc_go() bareos-database-common reconfigure 2171.
  dbc_config() bareos-database-common reconfigure 2171.
  dbc_set_dbtype_defaults() .
  dbc_detect_installed_dbtype() pgsql.
  _dbc_detect_installed_dbtype() pgsql.
  dbc_detect_installed_dbtype() mysql.
  _dbc_detect_installed_dbtype() mysql.
  dbc_register_debconf() .
  dbc_read_package_config() .
  dbc_preseed_package_debconf() .
  dbc_config() bareos-database-common reconfigure 2171.
  dbc_set_dbtype_defaults() pgsql.
  dbc_detect_installed_dbtype() pgsql.
  _dbc_detect_installed_dbtype() pgsql.
  dbc_detect_installed_dbtype() mysql.
  _dbc_detect_installed_dbtype() mysql.
  dbc_register_debconf() .
  dbc_get_app_pass() .
  dbconfig-common: writing config to /etc/dbconfig-common/bareos-database-common.conf
  Replacing config file /etc/dbconfig-common/bareos-database-common.conf with new version
  chown: invalid user: ‘postgres’
  unable to connect to postgresql server.
  error encountered creating user:
  runuser: user postgres does not exist
  dbconfig-common: bareos-database-common configure: noninteractive fail.
  dbconfig-common: bareos-database-common configure: ignoring errors from here forwards
  dbconfig-common: dumping pgsql database bareos to /var/tmp/bareos-database-common.bareos.2019-08-16-16.11.pgsql.pL2gNl.
  dbconfig-common: dropping old pgsql database bareos.
  populating database via sql...  done.
  dbconfig-common: flushing administrative password

  -- ERROR

  (c)root at tests:~$ debconf-show bareos-database-common | grep database-type
  * bareos-database-common/database-type: pgsql

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bareos/+bug/1840485/+subscriptions