Bug 1874043

Summary: [ESXi[RHEL8.3]The cloned VM network could not auto connect after customization with cloud-init
Product: Red Hat Enterprise Linux 8 Reporter: ldu <ldu>
Component: cloud-initAssignee: Virtualization Maintenance <virt-maint>
Status: CLOSED CURRENTRELEASE QA Contact: Virtualization Bugs <virt-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.3CC: boyang, eterrell, huzhao, jgreguske
Target Milestone: rc   
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-09-01 09:04:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
network status none

Description ldu 2020-08-31 11:46:28 UTC 
Description of problem: 
when clone an existing virtual machine, or deploy a virtual machine from a VM template in a folder, customize the guest operating system with cloud-init, the cloned vm network could not auto connect when boot up

Version-Release number of selected component (if applicable):
cloud-init-19.4-9.el8.noarch

How reproducible:
100%

Steps to Reproduce:
1. Create a RHEL8.3 esp2 VM on VMware ESXi host
2. Install cloud-init in guest with command #yum install cloud-init -y
3. Clone the VM and selcect customize the guest with specification
4. After clone completed, boot up the guest
5. Check the cloned vm network status

 
Actual results:
The cloned vm network not connected, the network status is disconnect on vSphere client.

Expected results:
The cloned vm network should connected.

Additional info:
This is a regression issue, the cloud-init-19.4-7.el8.noarch don't have this issue.
Comment 1 ldu 2020-08-31 12:00:01 UTC 
Created attachment 1713140 [details]
network status