RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Customize Guest uses static IP with cloud-init failed

Version-Release number of selected component (if applicable):
kernel-4.18.0-32.el8.x86_64
open-vm-tools-10.3.0-1.el8.x86_64
cloud-init-18.2-1.el8

How reproducible:
100%

Steps:
1. install one new RHEL8.0 guest on ESXi host
2. Boot the guests and make sure vmtoolsd server running
3. Edit /lib/systemd/system/vmtoolsd.service, add "before=cloud-init-local.service"
4. Install the cloud-init, edit /etc/cloud/cloud.cfg, add ‘disable_vmware_customization: false’ into it
5. Power off the Guest
6. Create a customization specification with a new host name, domain name, timezone, Static IP settings in the Network settings
7. Clone and customize the Guest with specification created at step5
8. Power on the Guest cloned
9. Verify the new host name, domain name, timezone and network setting customized correct or not on the Guest cloned


Actual results:
The static ip setting failed, the timezone setting successfully. 

Expected results:
The static ip setting should successfully.


Additional info:
Customize Guest uses DHCP IP with cloud-init works well

The Customize Guest uses static/DHCP IP with cloud-init works well on RHEL7.6.
I also tried without cloud-init clone VM with static IP works well on RHEL 8.

For cloud-init, the network render should be 'sysconfig' for RHEL distro. 

But on rhel 8, the expected files are not available which are used by cloud-init to detect 'sysconfig', so that cloud-init return no network render available. 

The files are '/etc/sysconfig/network-scripts/network-functions' and 'etc/sysconfig/network-scripts/ifdown-eth', see details on how cloud-init detects 'sysconfig' at https://github.com/cloud-init/cloud-init/blob/master/cloudinit/net/sysconfig.py#L656

rhel 8 has changes on networking, to support cloud-init customization on rhel8, either rhel8 change the network-scripts back to the same with rehl7.x or change cloud-init code on how to detect network render for RHEL distro.

Root cause is possibly a duplicate of bug 1602784.

Confirmed with Eduardo: This is a duplicate of 1602784.

*** This bug has been marked as a duplicate of bug 1602784 ***