When cloning a Linux virtual machine a new MAC address is assigned to the virtual machine, but configuration files are not updated

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

In VMware vRealize Automation (formerly known as VMware vCloud Automation Center) 4.5.x and 5.1.x:

• When cloning a Linux virtual machine, a new MAC address is assigned to the virtual machine, but the configuration files are not necessarily updated.
• Red Hat and Red Hat-derived (e.g. CentOS) Linux virtual machines store the MAC address of NIC’s in system configuration files, which can lead to benign messages during the boot-up process.
• The following error may be reported by the newly cloned virtual machine.
  
  Bringing up interface eth0: Device eth0 has different MAC address than expected, ignoring.

Environment

VMware vCloud Automation Center for Server 4.5.x
VMware vCloud Automation Center for Server 5.1.x
VMware vCloud Automation Center for Desktop 5.1.x

Cause

This is most likely caused by the MAC address being hard-coded in the configuration scripts.

Resolution

To resolve this issue, on the Template Linux system, edit /etc/sysconfig/network-scripts/ifcfg-eth0 by removing the line that resembles this:

MAC=<xx:xx:xx:xx:xx:xx>

Where "<xx:xx:xx:xx:xx:xx>" is, is the MAC address that needs to be scrubbed.

Additional Information

Linux 仮想マシンのクローンを作成すると、新しい MAC アドレスは仮想マシンに割り当てられるが、構成ファイルが更新されない