curtin network config ignored on UC16 images
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
curtin |
Fix Released
|
High
|
Ryan Harper |
Bug Description
When deploying a UC16 image via maas curtin writes network-config into the target system's to /etc/cloud/
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:
- id: ens3
mac_address: 52:54:00:08:d8:6b
mtu: 1500
name: ens3
subnets:
- address: 10.0.0.130/24
dns_
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
- Scott Moser (community): Approve
- Server Team CI bot: Approve (continuous-integration)
- Lee Trager (community): Needs Fixing
-
Diff: 65 lines (+34/-2)3 files modifiedcurtin/commands/curthooks.py (+1/-1)
examples/tests/ubuntu_core.yaml (+32/-0)
tests/unittests/test_curthooks.py (+1/-1)
Changed in curtin: | |
assignee: | nobody → Ryan Harper (raharper) |
importance: | Undecided → High |
status: | New → Confirmed |
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.