curtin network config ignored on UC16 images

Bug #1685000 reported by Ryan Harper
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
curtin
High
Ryan Harper

Bug Description

When deploying a UC16 image via maas curtin writes network-config into the target system's to /etc/cloud/cloud.cfg.d/50-network-config.cfg

This file and contents are ignored and the instance will use fallback network config (dhcp on first interface).

The issue is that curtin did not include the top-level key ('network') required for cloud-init to know the file contains network config.

Here;s an example config found to be written by curtin on a UC16 image

# cat 50-network-config.cfg
config:
- id: ens3
  mac_address: 52:54:00:08:d8:6b
  mtu: 1500
  name: ens3
  subnets:
  - address: 10.0.0.130/24
    dns_nameservers: []
    gateway: 10.0.0.1
    type: static
  type: physical
- address:
  - 10.0.0.2
  search:
  - maas
  type: nameserver
version: 1

Cloud-init doesn't detect this without a top-level 'network' key and uses fallback network config instead.

Related branches

Ryan Harper (raharper)
Changed in curtin:
assignee: nobody → Ryan Harper (raharper)
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Scott Moser (smoser) wrote : Fixed in Curtin 17.1

This bug is believed to be fixed in curtin in 17.1. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

Changed in curtin:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers