[Bug 1546688] Re: Upgrades to xenial fail when installing initscripts

[Martin Pitt]

There is nothing to fix here in the package really -- the trusty image
is most probably a trusty cloud image, and cloud images modify
/etc/default/rcS (they add a new variable there). This then triggers the
conffile prompt. So I suggest to either build the original images with
the out-of-the-box /etc/default/rcS (if you want to detect conffile
prompts, which is a good idea in general), or indeed use --force-
confnew.

** Package changed: sysvinit (Ubuntu) => auto-upgrade-testing

** Changed in: auto-upgrade-testing
     Assignee: Martin Pitt (pitti) => Max Brustkern (nuclearbob)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1546688

Title:
  Upgrades to xenial fail when installing initscripts

Status in Auto Upgrade Testing:
  New

Bug description:
  We're running daily tests upgrading cloud images to xenial. The basic wily images started failing to install initscripts as part of the upgrade on February 12 in qemu. Trusty images are showing the same issue, where the relevant parts of the output are:
  Setting up initscripts (2.88dsf-59.3ubuntu2) ...
  Installing new version of config file /etc/init.d/halt ...
  Installing new version of config file /etc/init.d/killprocs ...
  Installing new version of config file /etc/init.d/ondemand ...
  Installing new version of config file /etc/init.d/rc.local ...
  Installing new version of config file /etc/init.d/reboot ...
  Installing new version of config file /etc/init.d/sendsigs ...
  Installing new version of config file /etc/init.d/single ...
  Installing new version of config file /etc/init.d/umountfs ...
  Installing new version of config file /etc/init.d/umountnfs.sh ...
  Installing new version of config file /etc/init.d/umountroot ...

  Configuration file '/etc/default/rcS'
   ==> Modified (by you or by a script) since installation.
   ==> Package distributor has shipped an updated version.
     What would you like to do about it ?  Your options are:
      Y or I  : install the package maintainer's version
      N or O  : keep your currently-installed version
        D     : show the differences between the versions
        Z     : start a shell to examine the situation
   The default action is to keep your current version.
  *** rcS (Y/I/N/O/D/Z) [default=N] ?

  One example job is here:
  https://platform-qa-jenkins.ubuntu.com/view/Upgrade/job/upgrade_ubuntu-wily-xenial-basic-amd64_qemu/97/console

  The issues does not appear to occur during lxc upgrades, only qemu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-upgrade-testing/+bug/1546688/+subscriptions