sysconfig only applies subnet/route config to physical interfaces
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Fix Released
|
Medium
|
Ryan Harper |
Bug Description
cloud-init master
Testing bridging configuration. First, empty subnets break sysconfig rendering; this has been reported in other bugs), after that, the resulting ifcfg-br0 does not include the static network configuration. Upon closer examination the _render_
% cat bridge.yaml
network:
version: 1
config:
- type: physical
name: eth0
subnets:
- type: dhcp4
- type: physical
name: eth1
- type: physical
name: eth2
- type: bridge
name: br0
- eth1
- eth2
params:
- eth1 50
- eth2 75
- eth1 28
- eth2 14
- 1 eth1
- 2 eth2
subnets:
- type: static
After fixing the empty subnet issue, we can see in net-convert rendering of ifcfg-br0 is missing
the 192.168.14.2/24 address.
% cat target-
# Created by cloud-init on instance boot automatically, do not edit.
#
AGEING=250
BOOTPROTO=none
DEVICE=br0
NM_CONTROLLED=no
ONBOOT=yes
PRIO=22
STP=off
TYPE=Bridge
USERCTL=no
Changed in cloud-init: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
assignee: | nobody → Ryan Harper (raharper) |
Changed in cloud-init: | |
status: | Confirmed → Fix Committed |
This bug is believed to be fixed in cloud-init in 17.1. If this is still a problem for you, please make a comment and set the state back to New
Thank you.