[Bug 1789475] [NEW] [SRU] Update package to adhere to new openstack-pkg-tools debconf templating

[Corey Bryant]

Public bug reported:

[Impact]
The magnum package was originally built with an older version of openstack-pkg-tools. When it is rebuilt with the current version of openstack-pkg-tools that is in bionic, the postinst script fails. This is due to consolidation of debconf templating within openstack-pkg-tools.

For example the magnum-common.postinst script fails with:

root at b1:~# DEBCONF_DEBUG=developer exec /usr/share/debconf/frontend /var/lib/dpkg/info/magnum-common.postinst configure                                                                                    
debconf (developer): frontend started
debconf (developer): frontend running, package name is magnum-common
debconf (developer): starting /var/lib/dpkg/info/magnum-common.config configure
debconf (developer): <-- INPUT high magnum/configure_db
debconf (developer): --> 30 question skipped
debconf (developer): <-- GO
debconf (developer): --> 0 ok
debconf (developer): <-- GET magnum/configure_db
debconf (developer): --> 0 false
debconf (developer): <-- INPUT high magnum/configure_rabbit
debconf (developer): --> 10 "magnum/configure_rabbit" doesn't exist
debconf (developer): <-- GO
debconf (developer): --> 0 ok
debconf (developer): <-- GET magnum/configure_rabbit
debconf (developer): --> 10 magnum/configure_rabbit doesn't exist


[Test Case]
sudo DEBIAN_FRONTEND=noninteractive apt install magnum-api magnum-conductor

[Regression Potential]
The changes are cherry-picked from the cosmic/rocky version of the package which limits the regression potential.

[Discussion]

** Affects: cloud-archive
     Importance: Undecided
         Status: Invalid

** Affects: cloud-archive/queens
     Importance: Undecided
         Status: Triaged

** Affects: magnum (Ubuntu)
     Importance: Undecided
         Status: Invalid

** Affects: magnum (Ubuntu Bionic)
     Importance: Undecided
         Status: Triaged

** Also affects: magnum (Ubuntu Bionic)
   Importance: Undecided
       Status: New

** Changed in: magnum (Ubuntu)
       Status: New => Invalid

** Changed in: magnum (Ubuntu Bionic)
       Status: New => Triaged

** Also affects: cloud-archive
   Importance: Undecided
       Status: New

** Also affects: cloud-archive/queens
   Importance: Undecided
       Status: New

** Changed in: cloud-archive/queens
       Status: New => Triaged

** Changed in: cloud-archive
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1789475

Title:
  [SRU] Update package to adhere to new openstack-pkg-tools debconf
  templating

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive queens series:
  Triaged
Status in magnum package in Ubuntu:
  Invalid
Status in magnum source package in Bionic:
  Triaged

Bug description:
  [Impact]
  The magnum package was originally built with an older version of openstack-pkg-tools. When it is rebuilt with the current version of openstack-pkg-tools that is in bionic, the postinst script fails. This is due to consolidation of debconf templating within openstack-pkg-tools.

  For example the magnum-common.postinst script fails with:

  root at b1:~# DEBCONF_DEBUG=developer exec /usr/share/debconf/frontend /var/lib/dpkg/info/magnum-common.postinst configure                                                                                    
  debconf (developer): frontend started
  debconf (developer): frontend running, package name is magnum-common
  debconf (developer): starting /var/lib/dpkg/info/magnum-common.config configure
  debconf (developer): <-- INPUT high magnum/configure_db
  debconf (developer): --> 30 question skipped
  debconf (developer): <-- GO
  debconf (developer): --> 0 ok
  debconf (developer): <-- GET magnum/configure_db
  debconf (developer): --> 0 false
  debconf (developer): <-- INPUT high magnum/configure_rabbit
  debconf (developer): --> 10 "magnum/configure_rabbit" doesn't exist
  debconf (developer): <-- GO
  debconf (developer): --> 0 ok
  debconf (developer): <-- GET magnum/configure_rabbit
  debconf (developer): --> 10 magnum/configure_rabbit doesn't exist

  
  [Test Case]
  sudo DEBIAN_FRONTEND=noninteractive apt install magnum-api magnum-conductor

  [Regression Potential]
  The changes are cherry-picked from the cosmic/rocky version of the package which limits the regression potential.

  [Discussion]

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1789475/+subscriptions