kernel-packages team mailing list archive

[Paul Schyska <paul@xxxxxxxxxxx>]

This is breaking cloud-init on AWS for us with  16.04 hvm:ebs-ssd (ami-
7a138709).

The networking.service unit goes into failed state and cloud-init
metadata crawler fails and falls back to local DataSource, skipping
provisioning of ssh keys etc.

Jun 01 19:45:07 ip-172-31-13-182 ifup[928]: bound to 172.31.13.182 -- renewal in 1373 seconds.
Jun 01 19:45:07 ip-172-31-13-182 ifup[928]: run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 1
Jun 01 19:45:07 ip-172-31-13-182 ifup[928]: Failed to bring up ens3.
Jun 01 19:45:07 ip-172-31-13-182 systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Jun 01 19:45:07 ip-172-31-13-182 systemd[1]: Failed to start Raise network interfaces.
Jun 01 19:45:07 ip-172-31-13-182 systemd[1]: Dependency failed for Initial cloud-init job (metadata service crawler).
Jun 01 19:45:07 ip-172-31-13-182 systemd[1]: cloud-init.service: Job cloud-init.service/start failed with result 'dependency'.
Jun 01 19:45:07 ip-172-31-13-182 systemd[1]: networking.service: Unit entered failed state.
Jun 01 19:45:07 ip-172-31-13-182 systemd[1]: networking.service: Failed with result 'exit-code'.

[... snip ...]

Jun 01 19:45:09 ip-172-31-13-182 cloud-init[1347]: [CLOUDINIT]
cc_final_message.py[WARNING]: Used fallback datasource

FWIW, this happened after installing docker.io, which pulls in ubuntu-
fan as a dependency.

A manual `/usr/sbin/fanctl net start ens3` exits 1, without any output.


** Also affects: cloud-init
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1551747

Title:
  ubuntu-fan causes issues during network configuration

Status in cloud-init:
  New
Status in Snappy:
  Confirmed
Status in ubuntu-fan package in Ubuntu:
  Confirmed

Bug description:
  it seems that ubuntu-fan is causing issues with network configuration.

  On 16.04 daily image:

  root@localhost:~# snappy list
  Name                Date       Version          Developer
  canonical-pi2       2016-02-02 3.0              canonical
  canonical-pi2-linux 2016-02-03 4.3.0-1006-3     canonical
  ubuntu-core         2016-02-22 16.04.0-10.armhf canonical

  I see this when I'm activating a wifi card on a raspberry pi 2.

  root@localhost:~# ifdown wlan0
  ifdown: interface wlan0 not configured
  root@localhost:~# ifup wlan0
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/wlan0/c4:e9:84:17:31:9b
  Sending on   LPF/wlan0/c4:e9:84:17:31:9b
  Sending on   Socket/fallback
  DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3 (xid=0x81c0c95e)
  DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5 (xid=0x81c0c95e)
  DHCPREQUEST of 192.168.0.170 on wlan0 to 255.255.255.255 port 67 (xid=0x5ec9c081)
  DHCPOFFER of 192.168.0.170 from 192.168.0.251
  DHCPACK of 192.168.0.170 from 192.168.0.251
  RTNETLINK answers: File exists
  bound to 192.168.0.170 -- renewal in 17145 seconds.
  run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 1
  Failed to bring up wlan0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1551747/+subscriptions