New VMware from OVA Production No IP address

[Jack Bennett]

Hi, Trying to use container linux for the first time and followed "https://coreos.com/os/docs/latest/booting-on-vmware.html"

Booting the VM I see from the console login screen 4 ssh keys and an ipv6 address on ens192:fe80::250:56ff:fe9b:733f which I can actually ping from another machine on this vlan. We don't actually use ipv6 though

Here's my network config it's seemingly ignoring as configured in VM Settings Options>  vAppOptions> properties https://gist.github.com/anonymous/3708cca393b11b3f226e84e2cdce6fcf

I've even written this cloud-config;

```

# cloud-config

coreos:

    units:

        - name: 00-ens192.network

        runtime: true

        content: |

            [Match]

            Name=ens192

            [Network]

            Address=10.201.0.101/24

            Gateway=10.201.0.1

            DNS=10.201.0.11

```

Fallen at the first hurdle here any idea anyone?

[Mimmus]

It seems that configuring parameters during OVA deployment doesn't work :(
We pass network and cloud-config by guestinfo.* parameters in the .vmx file.

[Jack Bennett]

Yes indeed; Appended this to the end of the vmx and we're away and working. It's just quite a paint to edit the vmx files in the datastore. Could you clarify that this is exactly the same settings I could reconfigure with a config-drive instead?

guestinfo.dns.server.0 ="10.201.0.11"

guestinfo.dns.server.1 ="10.201.0.12"

guestinfo.hostname ="Container01"

guestinfo.interface.0.dhcp ="no"

guestinfo.interface.0.ip.0.address ="10.201.0.101/24"

guestinfo.interface.0.name ="ens192"

guestinfo.interface.0.role ="public"

guestinfo.interface.0.route.0.destination ="0.0.0.0/0"

guestinfo.interface.0.route.0.gateway ="10.201.0.1"

[paul...@coreos.com]

"It seems that configuring parameters during OVA deployment doesn't work :(

We pass network and cloud-config by guestinfo.* parameters in the .vmx file."

This sounds like a gnarly bug.

Mind adding a GH issue for better tracking?
https://github.com/coreos/bugs/issues/

[Mimmus]

Jack,
I use a Powershell script that poweroff VMs, download .vmx, modify it and upload again on the datastore.
I prefer guestinfo.* interface to config-drive method.

[Mimmus]

Actually, I'm avoiding to insert network parameters by hand, using an automated script to deploy new VMs.
I hope to be able to replicate the problem and open an issue as soon as possible.