Ubuntu
libvirt package

  1. Bug #708172
  2. Comment #2

Comment 2 for bug 708172

Revision history for this message
Clint Byrum (clint-fewbar) wrote :

Thomas, thank you for taking the time to file this bug report and help us make Ubuntu better!

The upstart job is, indeed, ignoring any settings that used to be set in /etc/default/libvirt-bin.

Seeing as there is no warning about this in the release notes or changelog, I think this is a regression, as it breaks on upgrade from lucid to maverick.

As a workaround, you can take all the settings from that file and manually add them to /etc/init/libvirt-bin.conf as

env KRB5_KTNAME=/etc/libvirt/krb5.keytab

There is no need for a special script to do that.

The fix should be to source /etc/default/libvirt-bin and respect the flags as they were before, at least until the release following the next LTS.

Marking Triaged ( as Ubuntu is upstream for the upstart job ) and setting Importance to Medium, as this is a regression on upgrade, but only affects users with non-default configurations.