yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1712678@xxxxxxxxxxxxxxxxxx>]

[Expired for cloud-init because there has been no activity for 60 days.]

** Changed in: cloud-init
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1712678

Title:
  cloud-init configuring networking even when configuration is already
  available.

Status in cloud-init:
  Expired
Status in MAAS:
  Expired

Bug description:
  Using MAAS 2.2.2 and newest CentOS image that uses cloud-init cloud-
  init-0.7.9+224.g681baff-1.el7.centos.noarch, network configuration is
  being create even when configuration already exists.

  MAAS deployed an image that configures network interface via custom
  curthooks on the image. However, cloud-init also creates network
  configuration:

  
  [centos@withkvm ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth0 
  # Created by cloud-init on instance boot automatically, do not edit.
  #
  BOOTPROTO=dhcp
  DEVICE=eth0
  HWADDR=52:54:00:03:02:6e
  NM_CONTROLLED=no
  ONBOOT=yes
  TYPE=Ethernet
  USERCTL=no

  ## Configuration created by custom curtin hook/config
  [centos@withkvm ~]$ cat /etc/sysconfig/network-scripts/ifcfg-ens3 
  TYPE="Ethernet"
  NM_CONTROLLED="no"
  USERCTL="yes"
  HWADDR="52:54:00:03:02:6E"
  ONBOOT="yes"
  BOOTPROTO="dhcp"
  PEERDNS="yes"
  PERSISTENT_DHCLIENT="1"

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