This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1763323

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  ubuntu_fan_smoke_test failed on 4.4 X-kvm kernel

Status in linux package in Ubuntu:
Status in linux-kvm package in Ubuntu:

Bug description:
  The "enable disable fan test" will fail with Xenial KVM kernel

  Error message:
    RTNETLINK answers: Operation not supported
    /usr/sbin/fanctl: ip link add ftun0 type vxlan id 16384000 dev ens4 dstport 
0 local fan-map
    /usr/sbin/fanctl: WARNING: ftun0: failed to configure address translation
    RTNETLINK answers: Cannot assign requested address
    iptables v1.6.0: Couldn't load target `fan-egress':No such file or directory

    Try `iptables -h' or 'iptables --help' for more information.
    iptables: Bad rule (does a matching rule exist in that chain?).
    iptables: Bad rule (does a matching rule exist in that chain?).
    iptables: No chain/target/match by that name.
    rm: cannot remove '/run/ubuntu-fan/nat-core': No such file or directory
    /usr/sbin/fanatic: unable to bring fan up, unable to configure

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1021-kvm 4.4.0-1021.26
  ProcVersionSignature: User Name 4.4.0-1021.26-kvm 4.4.117
  Uname: Linux 4.4.0-1021-kvm x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Thu Apr 12 10:22:57 2018
   PATH=(custom, no user)
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to