yahoo-eng-team team mailing list archive

[Andres Rodriguez <andreserl@xxxxxxxxxxxxx>]

Hi Jason,

This seems like a curtin or cloud-init issue, or even an Ubuntu issue
itself. Based on your logs, it seems e/n/i was configured but networking
doesn't come up, and that sounds due to having
/etc/network/interfaces.d/*.cfg. I'm gonna mark this invalid for MAAS
and open curtin/cloud-init taks. That said, please provide:

1. MAAS version
2. Curtin config (maas <user> machine get-curtin-config <system_id>)
3. Curtin version on the MAAS server
4. The contents of /etc/network/interfaces.d/*.cfg

** Also affects: curtin
   Importance: Undecided
       Status: New

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

** Changed in: maas
       Status: New => Invalid

-- 
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/1671274

Title:
  network interface doesn't come up after installation in VM

Status in cloud-init:
  New
Status in curtin:
  New
Status in MAAS:
  Invalid

Bug description:
  I'm installing into a VM. It commissions fine, and deploy works up to
  the point where it reboots after curtin finishes, but when it comes
  back up after reboot, the network interface is not brought up.  This
  means it never finishes deployment.

  Looking at syslog, there is a Failed to start Raise network interfaces
  error. You can see it in the attached screenshot.

  This VM worked fine up until a couple of months ago.

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