Comment 1 for bug 1625091

Revision history for this message
Anders Kaseorg (andersk) wrote : Re: openafs 1.6.18.3-1 ADT test failure with linux 4.8.0-11.12

That log shows openafs-modules-dkms successfully compiling with kernel 4.8. The only problem shown is openafs-fileserver failing to start.

Setting up openafs-fileserver (1.6.18.3-1) ...
Created symlink /etc/systemd/system/multi-user.target.wants/openafs-fileserver.service → /lib/systemd/system/openafs-fileserver.service.
Job for openafs-fileserver.service failed because the control process exited with error code.
See "systemctl status openafs-fileserver.service" and "journalctl -xe" for details.
invoke-rc.d: initscript openafs-fileserver, action "start" failed.
● openafs-fileserver.service - OpenAFS file and database server manager
   Loaded: loaded (/lib/systemd/system/openafs-fileserver.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2016-09-18 09:16:56 UTC; 5ms ago
  Process: 12244 ExecStop=/usr/bin/bos shutdown localhost -wait -localauth (code=exited, status=1/FAILURE)
  Process: 12242 ExecStart=/usr/sbin/bosserver $DAEMON_ARGS (code=exited, status=0/SUCCESS)

Sep 18 09:16:56 autopkgtest-lxc-hbkuie systemd[1]: Starting OpenAFS file and ...
Sep 18 09:16:56 autopkgtest-lxc-hbkuie bos[12244]: bos: could not find entry ...
Sep 18 09:16:56 autopkgtest-lxc-hbkuie bos[12244]: [1B blob data]
Sep 18 09:16:56 autopkgtest-lxc-hbkuie systemd[1]: openafs-fileserver.service...
Sep 18 09:16:56 autopkgtest-lxc-hbkuie systemd[1]: Failed to start OpenAFS fi...
Sep 18 09:16:56 autopkgtest-lxc-hbkuie systemd[1]: openafs-fileserver.service...
Sep 18 09:16:56 autopkgtest-lxc-hbkuie systemd[1]: openafs-fileserver.service...
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package openafs-fileserver (--configure):
 subprocess installed post-installation script returned error exit status 1

It’s hard to say what went wrong without knowing what’s behind those ellipses. However, since this test seems to have been run in an LXC container with host kernel 4.4.0-36-generic, this cannot possibly be related to kernel 4.8.