[Expired for cloud-init because there has been no activity for 60 days.]
** Changed in: cloud-init
Status: Incomplete => Expired
--
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/1888315
Title:
MAAS does not set type=VLAN for CentOS & RHEL
Status in cloud-init:
Expired
Status in MAAS:
Invalid
Bug description:
With MAAS v2.6 and v2.7, when creating a VLAN in CentOS/RHEL 7 & 8
images (before OS is deployed), the interface's VLAN configuration is
incorrect, and as a result it does not come up.
The definition in /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg is
defined correctly, for example:
- id: bond0.100
mtu: 1500
name: bond0.100
subnets:
- type: manual
type: vlan
vlan_id: 100
vlan_link: bond0
(In this case it's a bond, but it's same for just an interface like
eth0 or ens3)
However, the network configuration file /etc/sysconfig/network-
scripts/ifcfg-bond.100 has an incorrect TYPE entry:
# Created by cloud-init on instance boot automatically, do not edit.
#
BOOTPROTO=none
DEVICE=bond0.100
MTU=1500
ONBOOT=yes
PHYSDEV=bond0
TYPE=Ethernet
USERCTL=no
VLAN=yes
Removing the TYPE=Ethernet entry or changing to TYPE=VLAN fixes the
problem.
I don't know if this is a problem with MAAS or cloud-init in
/etc/yum.repos.d/cloud-init-el-stable.repo. If this is a known issue
with cloud-init in those EPEL repos, is there a workaround?
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1888315/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
