Thanks for your response, Christian, I wasn't very clear in my followup above, but it turns out the Customization.pm comes from vCenter. I would therefore be tempted to say the this behavior is VMware's fault, except that:
* the explicit eth0 reference turns out the harmless -- ifconfig eth0 is run, but its results aren't actually used * the behavior varies with the version of open-vm-tools * the contents of the customization files are the same in both situations, since they are built into vCenter It's definitely not clear to me if this is an Ubuntu issue, an upstream issue, or a VMware issue. Also, yes, 2:10.0.7-3227872-2ubuntu1 works fine with network interface ens192, but 2:10.2.0-3~ubuntu0.16.04.1 only works with eth0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782451 Title: open-vm-tools 2:10.2.0-3~ubuntu0.16.04.1 customization doesn't work with predictable network interface names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1782451/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
