I read into an mysql dh_apparmor case (bug 1435368) that was mentioned
that it might be related.
There as well a postinst call has issues due to not yet reloaded
apparmor profiles.
But the libvirt postinst already has:
for p in usr.sbin.libvirtd usr.lib.libvirt.virt-aa-helper ; do
profile="/etc/apparmor.d/$p"
if [ -f "$profile" ] && aa-status --enabled 2>/dev/null; then
apparmor_parser -r "$profile" || true
fi
done
While that lacks the --remove and the --purge-cache of the workaround it should
still update the profile.
Yet there is a '|| true', so one might have failed to reload and then trigger.
Also the libvirt postinst seems to intentionally carry all restarting code
AFTER the #DEBHELPER# section.
So the dh_apparmor code would run there I think and later code in the postinst
should only face the reloaded profiles.
I wonder how/where/which-log could confirmed that these reloads (the explicit
one from postinst and the apparmor one) failed ...? The service is restarted
automatically
Maybe if one can reproduce the case he could debug that.
So please:
1. if one can modify my steps-to-repro in a way that they trigger please let us
know
2. If one runs into this, before applying the workaround please check which
profiles are loaded.
Unfortunately I don't know a good way to check if the loaded one (assumed to
be old) matches the on disk profile (new after update).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1594902
Title:
Failed to upgrade to libvirt-bin 1.3.1-1ubuntu10.1 on Ubuntu 16.04
64-bit
Status in apparmor package in Ubuntu:
New
Status in libvirt package in Ubuntu:
Confirmed
Bug description:
Output from 'apt-get upgrade':
Setting up libvirt-bin (1.3.1-1ubuntu10.1) ...
initctl: Unable to connect to Upstart: Failed to connect to socket
/com/ubuntu/upstart: Connection refused
insserv: warning: script 'screen-cleanup' missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for script
`screen-cleanup'
insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script
`screen-cleanup'
initctl: Unable to connect to Upstart: Failed to connect to socket
/com/ubuntu/upstart: Connection refused
insserv: warning: script 'binfmt-support' missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for script
`binfmt-support'
insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script
`binfmt-support'
initctl: Unable to connect to Upstart: Failed to connect to socket
/com/ubuntu/upstart: Connection refused
insserv: warning: script 'screen-cleanup' missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for script
`screen-cleanup'
insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script
`screen-cleanup'
initctl: Unable to connect to Upstart: Failed to connect to socket
/com/ubuntu/upstart: Connection refused
insserv: warning: script 'binfmt-support' missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for script
`binfmt-support'
insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script
`binfmt-support'
initctl: Unable to connect to Upstart: Failed to connect to socket
/com/ubuntu/upstart: Connection refused
insserv: warning: script 'screen-cleanup' missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for script
`screen-cleanup'
insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script
`screen-cleanup'
initctl: Unable to connect to Upstart: Failed to connect to socket
/com/ubuntu/upstart: Connection refused
insserv: warning: script 'binfmt-support' missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for script
`binfmt-support'
insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script
`binfmt-support'
Job for libvirt-bin.service failed because the control process exited with
error code. See "systemctl status libvirt-bin.service" and "journalctl -xe" for
details.
invoke-rc.d: initscript libvirt-bin, action "restart" failed.
dpkg: error processing package libvirt-bin (--configure):
subprocess installed post-installation script returned error exit status 1
E: Sub-process /usr/bin/dpkg returned an error code (1)
Output from 'systemctl status libvirt-bin.service':
● libvirt-bin.service - Virtualization daemon
Loaded: loaded (/lib/systemd/system/libvirt-bin.service; enabled; vendor
preset: enabled)
Active: inactive (dead) (Result: exit-code) since Tue 2016-06-21 17:55:16
BST; 4min 52s ago
Docs: man:libvirtd(8)
http://libvirt.org
Process: 2984 ExecStart=/usr/sbin/libvirtd $libvirtd_opts (code=exited,
status=6)
Main PID: 2984 (code=exited, status=6)
Jun 21 17:55:15 lydia systemd[1]: Failed to start Virtualization daemon.
Jun 21 17:55:15 lydia systemd[1]: libvirt-bin.service: Unit entered failed
state.
Jun 21 17:55:15 lydia systemd[1]: libvirt-bin.service: Failed with result
'exit-code'.
Jun 21 17:55:16 lydia systemd[1]: libvirt-bin.service: Service hold-off time
over, scheduling restart.
Jun 21 17:55:16 lydia systemd[1]: Stopped Virtualization daemon.
Jun 21 17:55:16 lydia systemd[1]: libvirt-bin.service: Start request repeated
too quickly.
Jun 21 17:55:16 lydia systemd[1]: Failed to start Virtualization daemon.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1594902/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
