I've got a complicated and crazy set of circumstances I need to understand and work out a solution for.
Background: We release our product as a virtual appliance via OVFs. With our next-generation product I use packer to generate a gold image, and I give it a interfaces file with the adapter name ens160. Everything works fine there. However, we have an older product that we release the same way, except I don't have a packer script for it. I was previously using a vm that I put the changes on, then export it as an OVF.
Last week we had to do a bugfix for the old product. When I tried to export the OVF, the vcenter host it was on crapped out and wouldn't export it. So I moved it to the other host, which is where I build the packer based project.
The original machine had an ens160 name also, but when I migrated it to the other host, the name changed to ens32 and the networking service said ens160 isn't a valid name. But I KNOW ens160 is a valid name on this host. Listing the logical address only shows ens32.
Why did it change? How can I force it to use ens160 or have it generate the interfaces file at start up with the proper interface name? I'm having real trouble understanding the predictable network interface name thing. It doesn't seem very predictable.