yahoo-eng-team team mailing list archive

[Lukas Märdian <1879933@xxxxxxxxxxxxxxxxxx>]

The working example seems to set a default route in the legacy way, using the "gateway4" setting:
  gateway4: 10.245.168.1

While the broken example sets a default route (on routing table 1 only) in the new way, using the "routes" setting.
      routes:
      - table: 1
        to: 0.0.0.0/0
        via: 10.245.168.1
      routing-policy:
      - from: 10.245.168.0/21
        priority: 100
        table: 1
      - from: 10.245.168.0/21
        table: 254
        to: 10.245.168.0/21

Netplan seems to apply the configuration it gets correctly. But when the
default route is installed to "table 1" instead of the default routing
table, the setup is broken. So this is not a Netplan issue IMO, but
whatever provides the configuration (gateway4 vs routes) seems to be at
fault here. The default route should be provided using the routes
setting, but maybe just leaving out the "table: 1" and routing-policy
settings could fix this.

Please re-open (on the Netplan task), if you still think this is a
Netplan issue.

** Changed in: netplan
       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/1879933

Title:
  ppc64el / arm64 - issues with cloud-init setting default route

Status in cloud-init:
  Expired
Status in MAAS:
  Incomplete
Status in netplan:
  Invalid

Bug description:
  This is quite possibly a cloud-init bug.

  MAAS version: 2.6.2 (7841-ga10625be3-0ubuntu1~18.04.1)

  This problem manifests whether to machine is deployed with juju or
  manually via the MAAS ui.

  This problem is intermittent and I have only seen it affecting arm64
  and ppc64el machines (out of 29 machines in total) - all of these
  machines have 2 interfaces connected to the same fabric in the same
  subnet - one is set to unassigned to be used as a bridge port / data
  port for openstack deployments, the other is set to auto assign.

  This problem occurs with bionic, eoan and focal deployments.

  I have recommissioned the affected machines numerous times, including
  attempts to update firmware.

  Symptoms: when the machine comes up after it is deployed there is no
  default gateway, e.g.

  ubuntu@node-mawhile:/var/log$ ip route
  10.245.168.0/21 dev enP5p9s0f0 proto kernel scope link src 10.245.168.63 

  The rsyslog on the MAAS server shows that the machine is being
  configured correctly:

  https://pastebin.ubuntu.com/p/ZZzQ4q2ZCT/

  But the cloud-init log on the machine does not have a default gateway:

  https://pastebin.ubuntu.com/p/cCJbF7zhtK/

  
  Additional info:

  Something I have observed is that the machines where this problem
  occurs seem to sometimes have the 'unassigned' interface as the PXE
  interface, and sometimes the auto-assigned interface. I've tried to
  force this but the PXE interface moves around by itself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1879933/+subscriptions