cloud-init fails to configure bonding on CentOS 7
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Fix Released
|
Medium
|
Ryan Harper |
Bug Description
When using ppa:raharper/
cloud-init-
curtin-
[1] http://
apt:
preserve_
primary:
- arches:
- default
uri: http://
proxy: http://
security:
- arches:
- default
uri: http://
cloudconfig:
maas-
content: "#cloud-
\ metadata_url: 'http://
\ token_secret: 7jC2PWsGcrxcvHN
path: /etc/cloud/
maas-datasource:
content: 'datasource_list: [ MAAS ]'
path: /etc/cloud/
maas-ubuntu-sso:
content: '#cloud-config
snappy: {email: <email address hidden>}
'
path: /etc/cloud/
debconf_selections:
maas: 'cloud-init cloud-init/
cloud-init cloud-init/
cloud-init cloud-init/
cloud-init cloud-init/
false\n primary:\n - arches: [default]\n uri: http://
http://
true\
true\
H24Erg25Cx9
webhook}
{primary: ''http://
[''http://
arches: [default]\n failsafe: {primary: ''http://
security: ''http://
[''http://
'
install:
log_file: /tmp/install.log
post_files:
- /tmp/install.log
late_commands:
maas:
- wget
- --no-proxy
- http://
- --post-data
- op=netboot_off
- -O
- /dev/null
network:
config:
- id: ens10
mac_address: 52:54:00:4b:11:ea
mtu: 1500
name: ens10
subnets:
- type: manual
type: physical
- id: ens3
mac_address: 52:54:00:aa:40:cd
mtu: 1500
name: ens3
subnets:
- type: manual
type: physical
- bond_interfaces:
- ens10
- ens3
id: bond0
mac_address: 52:54:00:aa:40:cd
mtu: 1500
name: bond0
params:
bond-
bond-
bond-miimon: 100
bond-mode: active-backup
bond-updelay: 0
bond-
subnets:
- address: 10.0.0.147/24
dns_
gateway: 10.0.0.1
type: static
type: bond
- address:
- 10.0.0.2
search:
- maas
type: nameserver
version: 1
network_commands:
builtin:
- curtin
- net-meta
- custom
reporting:
maas:
consumer_key: 72gtz4EuywxY9wtaTy
endpoint: http://
token_key: H24Erg25Cx9Q8hHJrp
token_secret: 7jC2PWsGcrxcvHN
type: webhook
Related branches
- Server Team CI bot: Approve (continuous-integration)
- Ryan Harper: Approve
-
Diff: 224 lines (+159/-1)2 files modifiedcloudinit/net/sysconfig.py (+11/-0)
tests/unittests/test_net.py (+148/-1)
- cloud-init Commiters: Pending requested
-
Diff: 357 lines (+232/-3)4 files modifiedcloudinit/net/eni.py (+1/-1)
cloudinit/net/sysconfig.py (+18/-0)
cloudinit/sources/DataSourceAzure.py (+1/-1)
tests/unittests/test_net.py (+212/-1)
Changed in maas: | |
milestone: | none → 2.3.0 |
status: | New → Triaged |
status: | Triaged → Incomplete |
Changed in cloud-init: | |
status: | In Progress → Fix Committed |
assignee: | nobody → Ryan Harper (raharper) |
no longer affects: | maas |
Jun 30 02:02:39 localhost kernel: Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) /network- scripts/ ifup-eth] Device bond0 has different MAC address than expected, ignoring. network- scripts/ ifup-eth: Device bond0 has different MAC address than expected, ignoring.
Jun 30 02:02:39 localhost kernel: bond0: Setting MII monitoring interval to 100
Jun 30 02:02:39 localhost kernel: bond0: Setting xmit hash policy to layer2 (0)
Jun 30 02:02:39 localhost network: Bringing up interface bond0: ERROR : [/etc/sysconfig
Jun 30 02:02:39 localhost /etc/sysconfig/
Jun 30 02:02:39 localhost network: [FAILED]
Jun 30 02:02:39 localhost systemd: network.service: control process exited, code=exited status=1
Jun 30 02:02:39 localhost systemd: Failed to start LSB: Bring up/down networking.
Jun 30 02:02:39 localhost systemd: Unit network.service entered failed state.
Jun 30 02:02:39 localhost systemd: network.service failed.
In centos7; it doesn't like it when you specify a mac address for the bond itself (rather the bond will pick a mac from the slaves.
MAAS can *not* send a mac for a bond (unless someone is being explicit in the UI that they expect the bond to have a mac of <mac>).