yahoo-eng-team team mailing list archive

[Stephan Scheying <1811613@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

With cloud-init 18.5-1-g5b065316-0ubuntu1 and the following VMware
cust.cfg:

[NETWORK]
NETWORKING = yes
BOOTPROTO = dhcp
HOSTNAME = test
DOMAINNAME = zeit.de

[NIC-CONFIG]
NICS = NIC1

[NIC1]
MACADDR = 00:50:56:9e:ce:5f
ONBOOT = yes
IPv4_MODE = BACKWARDS_COMPATIBLE
BOOTPROTO = static
IPADDR = 10.100.4.238
NETMASK = 255.255.0.0
GATEWAY = 10.100.0.3


[DNS]
DNSFROMDHCP=no
SUFFIX|1 = zeit.de
NAMESERVER|1 = 172.20.10.7
NAMESERVER|2 = 172.20.10.2

[DATETIME]
TIMEZONE = Europe/Berlin
UTC = yes

The following output is productd by the netplan renderer:

network:
    version: 2
    ethernets:
        ens192:
            addresses:
            - 10.100.4.238/16
            match:
                macaddress: 00:50:56:9e:ce:5f
            nameservers:
                addresses:
                - 172.30.20.105
                - 172.20.10.3
                search: []
            routes:
            -   metric: 10000
                to: 10.100.0.0/16
                via: 10.100.0.3
            set-name: ens192

This leads to a missing default route. What I would expect is a
'gateay4' parameter for the interface. It is probably related to
https://github.com/cloud-init/cloud-
init/commit/cb44ad6f42ac015d7d8eaf2ab0bb5ab125ed04b6 which seems to
address a similar problem.

** 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/1811613

Title:
  OVF Vmware IMC does not render gateway to netplan

Status in cloud-init:
  New

Bug description:
  With cloud-init 18.5-1-g5b065316-0ubuntu1 and the following VMware
  cust.cfg:

  [NETWORK]
  NETWORKING = yes
  BOOTPROTO = dhcp
  HOSTNAME = test
  DOMAINNAME = zeit.de

  [NIC-CONFIG]
  NICS = NIC1

  [NIC1]
  MACADDR = 00:50:56:9e:ce:5f
  ONBOOT = yes
  IPv4_MODE = BACKWARDS_COMPATIBLE
  BOOTPROTO = static
  IPADDR = 10.100.4.238
  NETMASK = 255.255.0.0
  GATEWAY = 10.100.0.3

  
  [DNS]
  DNSFROMDHCP=no
  SUFFIX|1 = zeit.de
  NAMESERVER|1 = 172.20.10.7
  NAMESERVER|2 = 172.20.10.2

  [DATETIME]
  TIMEZONE = Europe/Berlin
  UTC = yes

  The following output is productd by the netplan renderer:

  network:
      version: 2
      ethernets:
          ens192:
              addresses:
              - 10.100.4.238/16
              match:
                  macaddress: 00:50:56:9e:ce:5f
              nameservers:
                  addresses:
                  - 172.30.20.105
                  - 172.20.10.3
                  search: []
              routes:
              -   metric: 10000
                  to: 10.100.0.0/16
                  via: 10.100.0.3
              set-name: ens192

  This leads to a missing default route. What I would expect is a
  'gateay4' parameter for the interface. It is probably related to
  https://github.com/cloud-init/cloud-
  init/commit/cb44ad6f42ac015d7d8eaf2ab0bb5ab125ed04b6 which seems to
  address a similar problem.

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