yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #74423
[Bug 1788915] [NEW] sysconfig renders vlan with TYPE=Ethernet
Public bug reported:
Distribution: Fedora 28
Cloud provider: None
Network content of /etc/cloud/cloud.cfg.d/99_datasource.cfg (omitting users, etc.):
network:
version: 1
config:
- type: physical
name: lan1
mac_address: 0c:c4:7a:db:dc:b0
- type: vlan
name: lan1.100
vlan_link: lan1
vlan_id: 100
subnets:
- type: static
address: 192.168.0.2/24
gateway: 192.168.0.1
dns_nameservers:
- 8.8.8.8
- 8.8.4.4
- type: vlan
name: lan1.3900
vlan_link: lan1
vlan_id: 3900
subnets:
- type: static
address: 10.1.0.2/16
gateway:
I am unable to attach logs (no network connection).
$ cloud-init --version
/usr/bin/cloud-init 17.1
The sysconfig renderer leaves the configured "kind" set to the default
(ethernet), which results in a config file with "TYPE=Ethernet", which
is incorrect and results in the VLAN interface not being created.
$ cat ifcfg-lan1.100
# Created by cloud-init on instance boot automatically, do not edit.
#
BOOTPROTO=none
DEFROUTE=yes
DEVICE=lan1.100
GATEWAY=192.168.0.1
IPADDR=192.168.0.2
NETMASK=255.255.255.0
ONBOOT=yes
PHYSDEV=lan1
TYPE=Ethernet
USERCTL=no
VLAN=yes
$ ifup lan1.100
Error: Connection activation failed: No suitable device found for this connection.
Removing the offending "TYPE=Ethernet" line from the config file
resolves the problem (as does changing it to "TYPE=Vlan").
I altered my configuration to use version 2 of the network configuration
data with identical results (problem is in renderer).
** Affects: cloud-init
Importance: Undecided
Status: New
--
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/1788915
Title:
sysconfig renders vlan with TYPE=Ethernet
Status in cloud-init:
New
Bug description:
Distribution: Fedora 28
Cloud provider: None
Network content of /etc/cloud/cloud.cfg.d/99_datasource.cfg (omitting users, etc.):
network:
version: 1
config:
- type: physical
name: lan1
mac_address: 0c:c4:7a:db:dc:b0
- type: vlan
name: lan1.100
vlan_link: lan1
vlan_id: 100
subnets:
- type: static
address: 192.168.0.2/24
gateway: 192.168.0.1
dns_nameservers:
- 8.8.8.8
- 8.8.4.4
- type: vlan
name: lan1.3900
vlan_link: lan1
vlan_id: 3900
subnets:
- type: static
address: 10.1.0.2/16
gateway:
I am unable to attach logs (no network connection).
$ cloud-init --version
/usr/bin/cloud-init 17.1
The sysconfig renderer leaves the configured "kind" set to the default
(ethernet), which results in a config file with "TYPE=Ethernet", which
is incorrect and results in the VLAN interface not being created.
$ cat ifcfg-lan1.100
# Created by cloud-init on instance boot automatically, do not edit.
#
BOOTPROTO=none
DEFROUTE=yes
DEVICE=lan1.100
GATEWAY=192.168.0.1
IPADDR=192.168.0.2
NETMASK=255.255.255.0
ONBOOT=yes
PHYSDEV=lan1
TYPE=Ethernet
USERCTL=no
VLAN=yes
$ ifup lan1.100
Error: Connection activation failed: No suitable device found for this connection.
Removing the offending "TYPE=Ethernet" line from the config file
resolves the problem (as does changing it to "TYPE=Vlan").
I altered my configuration to use version 2 of the network
configuration data with identical results (problem is in renderer).
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1788915/+subscriptions
Follow ups