[Yahoo-eng-team] [Bug 1835008] Re: network_v2 does not set mtu on eni config
Tracked in Github Issues as https://github.com/canonical/cloud- init/issues/3401 ** Bug watch added: github.com/canonical/cloud-init/issues #3401 https://github.com/canonical/cloud-init/issues/3401 ** Changed in: cloud-init Status: Confirmed => 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/1835008 Title: network_v2 does not set mtu on eni config Status in cloud-init: Expired Status in curtin: Invalid Status in MAAS: Invalid Bug description: The MTU is not set on the bond, nor vlans on the bond, nor the bridges attached to the vlans on a network_v2 configuration. It's only set on the underlying interfaces (eth0, eth1) This does not happen if given a network_v1 configuration. (I'm deploying ubuntu xenial via MAAS 2.6.0, setting force_v1_network_yaml=true is my current workaround.) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1835008/+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
[Yahoo-eng-team] [Bug 1835008] Re: network_v2 does not set mtu on eni config
for non-physical interfaces, common attributes like mtu were not copied into the internal state when merging v2 config. ** Changed in: curtin Status: New => Invalid ** Changed in: cloud-init Status: New => Confirmed -- 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/1835008 Title: network_v2 does not set mtu on eni config Status in cloud-init: Confirmed Status in curtin: Invalid Status in MAAS: Invalid Bug description: The MTU is not set on the bond, nor vlans on the bond, nor the bridges attached to the vlans on a network_v2 configuration. It's only set on the underlying interfaces (eth0, eth1) This does not happen if given a network_v1 configuration. (I'm deploying ubuntu xenial via MAAS 2.6.0, setting force_v1_network_yaml=true is my current workaround.) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1835008/+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
[Yahoo-eng-team] [Bug 1835008] Re: network_v2 does not set mtu on eni config
** Also affects: curtin Importance: Undecided Status: New ** Changed in: maas Status: New => Invalid -- 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/1835008 Title: network_v2 does not set mtu on eni config Status in cloud-init: New Status in curtin: New Status in MAAS: Invalid Bug description: The MTU is not set on the bond, nor vlans on the bond, nor the bridges attached to the vlans on a network_v2 configuration. It's only set on the underlying interfaces (eth0, eth1) This does not happen if given a network_v1 configuration. (I'm deploying ubuntu xenial via MAAS 2.6.0, setting force_v1_network_yaml=true is my current workaround.) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1835008/+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
[Yahoo-eng-team] [Bug 1835008] Re: network_v2 does not set mtu on eni config
** Description changed: The MTU is not set on the bond, nor vlans on the bond, nor the bridges attached to the vlans on a network_v2 configuration. It's only set on the underlying interfaces (eth0, eth1) This does not happen if given a network_v1 configuration. + + (I'm deploying ubuntu xenial via MAAS 2.6.0, setting + force_v1_network_yaml=true is my current workaround.) ** Also affects: maas 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/1835008 Title: network_v2 does not set mtu on eni config Status in cloud-init: New Status in MAAS: New Bug description: The MTU is not set on the bond, nor vlans on the bond, nor the bridges attached to the vlans on a network_v2 configuration. It's only set on the underlying interfaces (eth0, eth1) This does not happen if given a network_v1 configuration. (I'm deploying ubuntu xenial via MAAS 2.6.0, setting force_v1_network_yaml=true is my current workaround.) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1835008/+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